i18next-http-backend is a backend layer for i18next that loads translation resources in Node.js, browsers, and Deno. Prior to 4.0.2, attacker-controlled language or namespace values interpolated into a custom loadPath or addPath that begins directly with {{lng}} or {{ns}} can make colon-based input become an absolute URL or, in browsers, make a double-slash namespace become a protocol-relative URL. The resulting request can leave the intended origin and cause URL injection or server-side request forgery. The default /locales/{{lng}}/{{ns}}.json template and templates with a leading path or origin are not affected because the placeholder does not occupy the URL's structural beginning. This issue is fixed in version 4.0.2.
CVE-2026-105800
LOWPre-NVD 3.73.7Elevated
EchelonGraph scoreLOW confidence
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 3.7Exploit: Elevated riskExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 3.7
- EG Score
- 3.7LOWlow confidence
- EG Risk
- 33EG Risk 33/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 6, 2026
References (4)
- security-advisories@githubhttps://github.com/i18next/i18next-http-backend/commit/07e028862b25d0b9251bf3cafb92be2d35285f85
- security-advisories@githubhttps://github.com/i18next/i18next-http-backend/releases/tag/v4.0.2
- security-advisories@githubhttps://github.com/i18next/i18next-http-backend/security/advisories/GHSA-xvq9-wjp8-hwqf
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/i18next/i18next-http-backend/security/advisories/GHSA-xvq9-wjp8-hwqf
Vendor Advisories for CVE-2026-105800(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| i18next-http-backend | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-06 18:32 UTCEG score recompute
- 2026-10-06 17:26 UTCEG score recompute
- 2026-10-06 15:27 UTCEG score recompute
- 2026-10-06 14:55 UTCEG score recompute
- 2026-10-06 14:54 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(4)
What is CVE-2026-105800?
CVE-2026-105800 is a low vulnerability published on October 6, 2026. i18next-http-backend is a backend layer for i18next that loads translation resources in Node.js, browsers, and Deno. Prior to 4.0.2, attacker-controlled language or namespace values interpolated into a custom loadPath or addPath that begins directly with {{lng}} or {{ns}} can make colon-based input…
When was CVE-2026-105800 disclosed?
CVE-2026-105800 was first published on October 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-105800?
CVE-2026-105800 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-105800?
A fix for CVE-2026-105800 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105800 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-105800
Is Your Infrastructure Affected by CVE-2026-105800?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.