VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

i18next: vulnerability history, versions and safety

i18next is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Jul 2018 to Nov 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all i18next vulnerabilities

Vulert verdict on i18next 26.5.6 i

Updated on 23 Oct 2026

Good news: 26.5.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 26.5.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 26.5.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 26.5.6 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Nov 2018 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Stars 8,647 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for i18next, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
26.5.6 22 Oct 2026 none MIT — Details →
26.5.5 22 Oct 2026 none MIT — Details →
26.5.4 21 Oct 2026 none MIT — Details →
26.5.3 19 Oct 2026 none MIT — Details →
26.5.2 17 Oct 2026 none MIT — Details →
26.5.1 17 Oct 2026 none MIT — Details →
26.5.0 17 Oct 2026 none MIT — Details →
26.4.7 16 Oct 2026 none MIT — Details →
26.4.6 15 Oct 2026 none MIT — Details →
26.4.5 14 Oct 2026 none MIT — Details →
26.4.4 12 Oct 2026 none MIT — Details →
26.4.3 10 Oct 2026 none MIT — Details →
26.4.2 03 Sep 2026 none MIT — Details →
26.4.1 01 Sep 2026 none MIT — Details →
26.4.0 20 Aug 2026 none MIT — Details →
26.3.6 09 Jul 2026 none MIT — Details →
26.3.5 08 Jul 2026 none MIT — Details →
26.3.4 30 Jun 2026 none MIT — Details →
26.3.3 26 Jun 2026 none MIT — Details →
26.3.2 24 Jun 2026 none MIT — Details →
26.3.1 03 Jun 2026 none MIT — Details →
26.3.0 26 May 2026 none MIT — Details →
26.2.0 14 May 2026 none MIT — Details →
26.1.0 11 May 2026 none MIT — Details →
26.0.10 07 May 2026 none MIT — Details →
26.0.9 06 May 2026 none MIT — Details →
26.0.8 24 Apr 2026 none MIT — Details →
26.0.7 23 Apr 2026 none MIT — Details →
26.0.6 18 Apr 2026 none MIT — Details →
26.0.5 15 Apr 2026 none MIT — Details →
26.0.4 08 Apr 2026 none MIT — Details →
26.0.3 31 Mar 2026 none MIT — Details →
26.0.2 30 Mar 2026 none MIT — Details →
26.0.1 28 Mar 2026 none MIT — Details →
26.0.0 28 Mar 2026 none MIT — Details →
25.10.10 26 Mar 2026 none MIT — Details →
25.10.9 24 Mar 2026 none MIT — Details →
25.10.8 24 Mar 2026 none MIT — Details →
25.10.7 24 Mar 2026 none MIT — Details →
25.10.6 24 Mar 2026 none MIT — Details →
25.10.5 23 Mar 2026 none MIT — Details →
25.10.4 22 Mar 2026 none MIT — Details →
25.10.3 21 Mar 2026 none MIT — Details →
25.10.2 21 Mar 2026 none MIT — Details →
25.10.1 21 Mar 2026 none MIT — Details →
25.10.0 21 Mar 2026 none MIT — Details →
25.9.0 20 Mar 2026 none MIT — Details →
25.8.20 19 Mar 2026 none MIT — Details →
25.8.19 19 Mar 2026 none MIT — Details →
25.8.18 11 Mar 2026 none MIT — Details →
25.8.17 09 Mar 2026 none MIT — Details →
25.8.16 09 Mar 2026 none MIT — Details →
25.8.15 09 Mar 2026 none MIT — Details →
25.8.14 04 Mar 2026 none MIT — Details →
25.8.13 20 Feb 2026 none MIT — Details →
25.8.12 20 Feb 2026 none MIT — Details →
25.8.11 18 Feb 2026 none MIT — Details →
25.8.10 16 Feb 2026 none MIT — Details →
25.8.9 16 Feb 2026 none MIT — Details →
25.8.8 15 Feb 2026 none MIT — Details →
25.8.7 13 Feb 2026 none MIT — Details →
25.8.6 12 Feb 2026 none MIT — Details →
25.8.5 11 Feb 2026 none MIT — Details →
25.8.4 05 Feb 2026 none MIT — Details →
25.8.3 04 Feb 2026 none MIT — Details →
25.8.2 04 Feb 2026 none MIT — Details →
25.8.1 03 Feb 2026 none MIT — Details →
25.8.0 20 Jan 2026 none MIT — Details →
25.7.4 07 Jan 2026 none MIT — Details →
25.7.3 15 Dec 2025 none MIT — Details →
25.7.2 08 Dec 2025 none MIT — Details →
25.7.1 01 Dec 2025 none MIT — Details →
25.7.0 01 Dec 2025 none MIT — Details →
25.6.3 19 Nov 2025 none MIT — Details →
25.6.2 11 Nov 2025 none MIT — Details →
25.6.1 06 Nov 2025 none MIT — Details →
25.6.0 10 Oct 2025 none MIT — Details →
25.5.3 01 Oct 2025 none MIT — Details →
25.5.2 05 Sep 2025 none MIT — Details →
25.5.1 05 Sep 2025 none MIT — Details →
25.5.0 04 Sep 2025 none MIT — Details →
25.4.2 24 Aug 2025 none MIT — Details →
25.4.1 23 Aug 2025 none MIT — Details →
25.4.0 20 Aug 2025 none MIT — Details →
25.3.6 14 Aug 2025 none MIT — Details →
25.3.5 14 Aug 2025 none MIT — Details →
25.3.4 10 Aug 2025 none MIT — Details →
25.3.3 10 Aug 2025 none MIT — Details →
25.3.2 09 Jul 2025 none MIT — Details →
25.3.1 04 Jul 2025 none MIT — Details →
25.3.0 30 Jun 2025 none MIT — Details →
25.2.1 25 May 2025 none MIT — Details →
25.2.0 19 May 2025 none MIT — Details →
25.1.3 14 May 2025 none MIT — Details →
25.1.2 08 May 2025 none MIT — Details →
25.1.1 06 May 2025 none MIT — Details →
25.1.0 06 May 2025 none MIT — Details →
25.0.2 28 Apr 2025 none MIT — Details →
25.0.1 20 Apr 2025 none MIT — Details →
25.0.0 15 Apr 2025 none MIT — Details →
24.2.3 13 Mar 2025 none — — Details →
24.2.2 25 Jan 2025 none — — Details →
24.2.1 06 Jan 2025 none — — Details →
24.2.0 20 Dec 2024 none — — Details →
24.1.2 17 Dec 2024 none — — Details →
24.1.1 17 Dec 2024 none — — Details →
24.1.0 11 Dec 2024 none — — Details →
24.0.5 03 Dec 2024 none — — Details →
24.0.4 03 Dec 2024 none — — Details →
24.0.3 03 Dec 2024 none — — Details →
24.0.2 25 Nov 2024 none — — Details →
24.0.1 25 Nov 2024 none — — Details →
24.0.0 22 Nov 2024 none — — Details →
23.16.8 20 Nov 2024 none — — Details →
23.16.7 20 Nov 2024 none — — Details →
23.16.6 19 Nov 2024 none — — Details →
23.16.5 08 Nov 2024 none — — Details →
23.16.4 25 Oct 2024 none — — Details →
23.16.3 24 Oct 2024 none — — Details →
23.16.2 20 Oct 2024 none — — Details →

The newest 120 of 620 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for i18next

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16010: Cross-Site Scripting in i18next 6.1 medium 3.4.4 24 Jul 2018
CVE-2017-16008: Cross-Site Scripting in i18next 6.1 medium 1.10.3 09 Nov 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About i18next

Is i18next safe to use?

Vulert records 2 vulnerabilities for i18next in npm: 0 critical, 0 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is i18next's Vulert package health score?

Vulert scores i18next 85/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of i18next affected?

No. 26.5.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does i18next have?

2 vulnerabilities are recorded for i18next in the npm ecosystem: 0 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new i18next vulnerabilities disclosed?

0 vulnerabilities were recorded for i18next in the last 12 months, and the oldest entry in this database dates to 24 Jul 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of i18next are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor i18next for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the i18next version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.