CVE-2026-41691

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 84% of all CVEs by exploit prediction. 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: epss, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Copilot said: i18nextify is a JavaScript library that adds i18nextify is a JavaScript library that adds website internationalization via a script tag, without source code changes. Versions prior to 3.0.5 interpolate the lng and ns values directly into the configured loadPath / addPath URL template without any encoding, validation, or path sanitisation. When an application exposes the language-code selection to user-controlled input (the default — i18next-browser-languagedetector reads ?lng= query params, cookies, localStorage, and request headers), an attacker can inject characters that change the structure of the outgoing request URL. This is a single URL-injection vulnerability. The attacker-controlled value is neutralised before it is used as part of an output URL string; the attack shape covers both path traversal and broader URL-structure injection — both are closed by the one interpolateUrl sanitisation fix. This issue has been fixed in version 3.0.5. If users cannot upgrade immediately, they can work around the issue by sanitising lng / ns before they reach i18next (strip .., /, \, ?, #, %, whitespace, and control characters; cap the length).

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
16.4%
KEV
Not listed

Published

May 7, 2026

Last Modified

May 29, 2026

Advisory Details (2)

Auto-updated May 7, 2026
Patch available. Sources: github.
github Patch Available

Path traversal / URL injection via unsanitised lng/ns in i18next-http-backend · Advisory · i18next/i18next-http-backend · GitHub

https://github.com/i18next/i18next-http-backend/security/advisories/GHSA-q89c-q3h5-w34g
generic

security: hardening for 3.0.5 · i18next/i18next-http-backend@4cee84f · GitHub

https://github.com/i18next/i18next-http-backend/commit/4cee84f229c637b9c182366d3156f726d407a621

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
i18next-http-backend3.0.5

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Frequently asked(5)

What is CVE-2026-41691?
CVE-2026-41691 is a medium vulnerability published on May 7, 2026. Copilot said: i18nextify is a JavaScript library that adds i18nextify is a JavaScript library that adds website internationalization via a script tag, without source code changes. Versions prior to 3.0.5 interpolate the lng and ns values directly into the configured loadPath / addPath URL template…
When was CVE-2026-41691 disclosed?
CVE-2026-41691 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41691 actively exploited?
CVE-2026-41691 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41691?
CVE-2026-41691 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-41691?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41691, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41691

Explore →

Is Your Infrastructure Affected by CVE-2026-41691?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.