i18next-http-middleware is a middleware to be used with Node.js web frameworks like express or Fastify and also for Deno. Prior to version 3.9.3, i18next-http-middleware passes the user-controlled lng and ns values from getResourcesHandler directly into i18next.services.backendConnector.load(languages, namespaces, …) without any sanitization. Depending on which backend is configured, the unvalidated path segments enable either path traversal or SSRF. This issue has been patched in version 3.9.3.
Project Subscriptions
No data.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-jfgf-83c5-2c4m | i18next-http-middleware has path traversal / SSRF via user-controlled language and namespace parameters |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 08 May 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | i18next-http-middleware is a middleware to be used with Node.js web frameworks like express or Fastify and also for Deno. Prior to version 3.9.3, i18next-http-middleware passes the user-controlled lng and ns values from getResourcesHandler directly into i18next.services.backendConnector.load(languages, namespaces, …) without any sanitization. Depending on which backend is configured, the unvalidated path segments enable either path traversal or SSRF. This issue has been patched in version 3.9.3. | |
| Title | Path traversal / SSRF in i18next-http-middleware via user-controlled language and namespace parameters | |
| Weaknesses | CWE-22 CWE-918 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-08T15:29:55.900Z
Reserved: 2026-04-26T13:26:14.515Z
Link: CVE-2026-42353
No data.
Status : Received
Published: 2026-05-08T16:16:12.197
Modified: 2026-05-08T16:16:12.197
Link: CVE-2026-42353
No data.
OpenCVE Enrichment
Updated: 2026-05-08T19:15:14Z
Github GHSA