CVE-2026-41693

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem. Prior to version 2.6.4, i18next-fs-backend substitutes the lng and ns options directly into the configured loadPath / addPath templates and then read / write the resulting file from disk. The interpolation is unencoded and unvalidated, so a crafted lng or ns value — containing .., a path separator, a control character, a prototype key, or simply an unexpectedly long string — allows an attacker who can influence either value to read or overwrite files outside the intended locale directory. When lng / ns are derived from untrusted input (request-scoped i18next instances behind an HTTP layer such as i18next-http-middleware, or any framework that lets the end user pick the language via query string, cookie, or header), a single request such as ?lng=../../../../etc/passwd causes the backend to attempt to read that path. This issue has been patched in version 2.6.4.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/100

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 computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

Published

May 8, 2026

Last Modified

May 12, 2026

Advisory Details (1)

Auto-updated May 8, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Path traversal via unsanitised lng/ns in i18next-fs-backend allows arbitrary file read / overwrite · Advisory · i18next/i18next-fs-backend · GitHub

https://github.com/i18next/i18next-fs-backend/security/advisories/GHSA-8847-338w-5hcj

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
i18next-fs-backend—
  • every version up to 2.6.4: fixed in 2.6.4
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 22× 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.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 07:58 UTCOSV refresh
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-23 17:53 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 19:31 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-12 15:01 UTCEPSS rescore
  21. 2026-09-11 14:23 UTCOSV refresh
  22. 2026-09-11 09:37 UTCEPSS rescore
  23. 2026-09-10 09:34 UTCEPSS rescore
  24. 2026-09-08 22:00 UTCEPSS rescore
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-23 19:00 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 11:30 UTCEG score recompute
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 04:33 UTCEG score recompute
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 03:07 UTCEG score recompute
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-12 16:43 UTCEG score recompute
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-11 15:51 UTCEG score recompute
  29. 2026-08-11 13:43 UTCEPSS rescore
  30. 2026-08-11 01:16 UTCEG score recompute
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 00:42 UTCEG score recompute
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 02:23 UTCEG score recompute
  35. 2026-08-08 16:37 UTCEPSS rescore
  36. 2026-08-07 19:30 UTCEG score recompute
  37. 2026-08-06 20:27 UTCEG score recompute
  38. 2026-08-06 13:46 UTCEPSS rescore
  39. 2026-08-05 22:07 UTCEG score recompute
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-04 15:10 UTCEPSS rescore
  42. 2026-08-04 10:38 UTCEPSS rescore
  43. 2026-08-03 19:30 UTCEG score recompute
  44. 2026-08-03 10:36 UTCEPSS rescore
  45. 2026-08-02 02:40 UTCEG score recompute
  46. 2026-08-02 02:27 UTCEPSS rescore
  47. 2026-08-01 04:16 UTCEPSS rescore
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-28 15:36 UTCEPSS rescore
  51. 2026-07-27 14:13 UTCEPSS rescore
  52. 2026-07-26 14:54 UTCEPSS rescore
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-25 14:18 UTCEPSS rescore
  55. 2026-07-24 14:17 UTCEPSS rescore
  56. 2026-07-23 14:18 UTCEPSS rescore
  57. 2026-07-23 03:11 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescore
  59. 2026-07-21 15:24 UTCEPSS rescore
  60. 2026-07-20 17:08 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 02:29 UTCEPSS rescore
  63. 2026-07-18 10:04 UTCEPSS rescore
  64. 2026-07-16 17:03 UTCEPSS rescore
  65. 2026-07-16 04:19 UTCOSV refresh
  66. 2026-07-15 16:57 UTCEPSS rescore
  67. 2026-07-15 02:00 UTCEPSS rescore
  68. 2026-07-13 22:30 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-09 19:10 UTCEPSS rescore
  74. 2026-07-08 15:15 UTCEPSS rescore
  75. 2026-07-07 13:46 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

1 shown

npm:i18next-fs-backend

Frequently asked(5)

What is CVE-2026-41693?
CVE-2026-41693 is a high vulnerability published on May 8, 2026. i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem. Prior to version 2.6.4, i18next-fs-backend substitutes the lng and ns options directly into the configured loadPath / addPath templates and then read / write the resulting file…
When was CVE-2026-41693 disclosed?
CVE-2026-41693 was first published on May 8, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41693 actively exploited?
CVE-2026-41693 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41693?
CVE-2026-41693 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-41693?
A fix for CVE-2026-41693 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41693?

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

Book a Demo →Browse All CVEs