Server-side Request Forgery (SSRF) Affecting i18next-http-middleware package, versions <3.9.3
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-I18NEXTHTTPMIDDLEWARE-16415528
- published4 May 2026
- disclosed29 Apr 2026
- creditUnknown
Introduced: 29 Apr 2026
NewCVE-2026-42353 (opens in a new tab)How to fix?
Upgrade i18next-http-middleware to version 3.9.3 or higher.
Overview
i18next-http-middleware is an i18next-http-middleware is a middleware to be used with Node.js web frameworks like express or Fastify and also for Deno.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the lng and ns parameters used by getResourcesHandler(). An attacker can access arbitrary files on the filesystem or make unauthorized network requests that expose internal resources. When the lng or ns parameter is interpolated into the path for a request, it can traverse to unintended local directories or reach out to unintended network locations, depending on the backend in use.
PoC
GET /locales/resources.json?lng=../../etc/passwd&ns=root