VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

i18next-http-backend: vulnerability history, versions and safety

i18next-http-backend is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 78 releases, from Apr 2026 to Oct 2026. 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 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 06 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all i18next-http-backend vulnerabilities

Vulert verdict on i18next-http-backend 4.0.4 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 4.0.4 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 06 Oct 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 95 packages i
  • Stars 527 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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-http-backend, 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
4.0.4 18 Oct 2026 none MIT — Details →
4.0.3 14 Oct 2026 none MIT — Details →
4.0.2 02 Sep 2026 none MIT — Details →
4.0.1 28 Jul 2026 L1 MIT Yes Details →
4.0.0 04 May 2026 L1 MIT Yes Details →
3.0.6 23 Apr 2026 L1 MIT Yes Details →
3.0.5 18 Apr 2026 L1 MIT Yes Details →
3.0.4 31 Mar 2026 M1 L1 MIT Yes Details →
2.7.3 23 Jan 2025 M1 L1 MIT Yes Details →
2.7.2 23 Jan 2025 M1 L1 MIT Yes Details →
3.0.2 23 Jan 2025 M1 L1 MIT Yes Details →
3.0.1 21 Nov 2024 M1 L1 MIT Yes Details →
2.7.1 21 Nov 2024 M1 L1 MIT Yes Details →
3.0.0 21 Nov 2024 M1 L1 MIT Yes Details →
2.7.0 20 Nov 2024 M1 L1 MIT Yes Details →
2.6.2 03 Oct 2024 M1 L1 MIT Yes Details →
2.6.1 21 Aug 2024 M1 L1 MIT Yes Details →
2.6.0 19 Aug 2024 M1 L1 MIT Yes Details →
2.5.2 17 May 2024 M1 L1 MIT Yes Details →
2.5.1 18 Apr 2024 M1 L1 MIT Yes Details →
2.5.0 21 Feb 2024 M1 L1 MIT Yes Details →
2.4.3 31 Jan 2024 M1 L1 MIT Yes Details →
2.4.2 20 Nov 2023 M1 L1 MIT Yes Details →
2.4.1 10 Nov 2023 M1 L1 MIT Yes Details →
2.4.0 10 Nov 2023 M1 L1 MIT Yes Details →
2.3.1 28 Oct 2023 M1 L1 MIT Yes Details →
2.3.0 25 Oct 2023 M1 L1 MIT Yes Details →
2.2.2 03 Sep 2023 M1 L1 MIT Yes Details →
2.2.1 18 May 2023 M1 L1 MIT Yes Details →
2.2.0 14 Mar 2023 M1 L1 MIT Yes Details →
2.1.1 19 Dec 2022 M1 L1 MIT Yes Details →
2.1.0 10 Dec 2022 M1 L1 MIT Yes Details →
2.0.2 25 Nov 2022 M1 L1 MIT Yes Details →
2.0.1 01 Nov 2022 M1 L1 MIT Yes Details →
2.0.0 26 Oct 2022 M1 L1 MIT Yes Details →
1.4.5 26 Oct 2022 M1 L1 MIT Yes Details →
1.4.4 20 Sep 2022 M1 L1 MIT Yes Details →
1.4.3 20 Sep 2022 M1 L1 MIT Yes Details →
1.4.2 19 Sep 2022 M1 L1 MIT Yes Details →
1.4.1 25 May 2022 M1 L1 MIT Yes Details →
1.4.0 13 Mar 2022 M1 L1 MIT Yes Details →
1.3.2 21 Jan 2022 M1 L1 MIT Yes Details →
1.3.1 07 Sep 2021 M1 L1 MIT Yes Details →
1.3.0 28 Jul 2021 M1 L1 MIT Yes Details →
1.2.8 24 Jul 2021 M1 L1 MIT Yes Details →
1.2.7 21 Jul 2021 M1 L1 MIT Yes Details →
1.2.6 25 May 2021 M1 L1 MIT Yes Details →
1.2.5 25 May 2021 M1 L1 MIT Yes Details →
1.2.4 12 May 2021 M1 L1 MIT Yes Details →
1.2.3 12 May 2021 M1 L1 MIT Yes Details →
1.2.2 28 Apr 2021 M1 L1 MIT Yes Details →
1.2.1 25 Mar 2021 M1 L1 MIT Yes Details →
1.2.0 22 Mar 2021 M1 L1 MIT Yes Details →
1.1.1 24 Feb 2021 M1 L1 MIT Yes Details →
1.1.0 29 Jan 2021 M1 L1 MIT Yes Details →
1.0.24 27 Jan 2021 M1 L1 MIT Yes Details →
1.0.23 25 Jan 2021 M1 L1 MIT Yes Details →
1.0.22 17 Jan 2021 M1 L1 MIT Yes Details →
1.0.21 22 Sep 2020 M1 L1 MIT Yes Details →
1.0.20 15 Sep 2020 M1 L1 MIT Yes Details →
1.0.19 11 Sep 2020 M1 L1 MIT Yes Details →
1.0.18 13 Aug 2020 M1 L1 MIT Yes Details →
1.0.17 15 Jul 2020 M1 L1 MIT Yes Details →
1.0.16 01 Jul 2020 M1 L1 MIT Yes Details →
1.0.15 02 Jun 2020 M1 L1 MIT Yes Details →
1.0.14 02 Jun 2020 M1 L1 MIT Yes Details →
1.0.13 29 May 2020 M1 L1 MIT Yes Details →
1.0.12 21 May 2020 M1 L1 MIT Yes Details →
1.0.11 15 May 2020 M1 L1 MIT Yes Details →
1.0.10 13 May 2020 M1 L1 MIT Yes Details →
1.0.9 11 May 2020 M1 L1 MIT Yes Details →
1.0.8 02 May 2020 M1 L1 MIT Yes Details →
1.0.7 28 Apr 2020 M1 L1 MIT Yes Details →
1.0.6 24 Apr 2020 M1 L1 MIT Yes Details →
1.0.5 24 Apr 2020 M1 L1 MIT Yes Details →
1.0.4 18 Apr 2020 M1 L1 MIT Yes Details →
1.0.3 15 Apr 2020 M1 L1 MIT Yes Details →
1.0.2 14 Apr 2020 M1 L1 MIT Yes Details →
1.0.1 14 Apr 2020 M1 L1 MIT Yes Details →
1.0.0 14 Apr 2020 M1 L1 MIT Yes Details →
0.0.1-security 14 Apr 2020 M1 L1 MIT Yes Details →

All 81 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for i18next-http-backend

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Path Traversal and URL Injection Vulnerability in i18next-http-backend 6.5 medium 3.0.5 22 Apr 2026
CVE-2026-105800: i18next-http-backend SSRF Vulnerability Due to Incomplete URL Validation 3.7 low 4.0.2 06 Oct 2026

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-http-backend

Is i18next-http-backend safe to use?

Vulert records 2 vulnerabilities for i18next-http-backend in npm: 0 critical, 0 high, 1 medium and 1 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-http-backend's Vulert package health score?

Vulert scores i18next-http-backend 73/100, which reads as in good shape. 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-http-backend affected?

No. 4.0.4, 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-http-backend have?

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

How often are new i18next-http-backend vulnerabilities disclosed?

2 vulnerabilities were recorded for i18next-http-backend in the last 12 months, and the oldest entry in this database dates to 22 Apr 2026. 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-http-backend 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-http-backend for upcoming vulnerabilities?

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