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 79% 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.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

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.2(medium)
EPSS
21.0%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 12, 2026

Advisory Details (1)

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

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 rangeFixed inDependents
i18next-fs-backend—2.6.4—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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 110 total refreshes for this CVE.

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

Related CVEs(same CWE)

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 in the National Vulnerability Database 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 21.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41693, 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-41693

Explore →

Is Your Infrastructure Affected by CVE-2026-41693?

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

Start Free Scan →Browse All CVEs