High severity · published May 8, 2026
CVE-2026-41690
Prototype pollution and path traversal in i18next-http-middleware via user-controlled language and namespace parameters
8.6
CVSS
0.3%
EPSS
No
On KEV
Description
18next-http-middleware is a middleware to be used with Node.js web frameworks like express or Fastify and also for Deno. Versions prior to 3.9.3 allow an unauthenticated HTTP client to pollute Object.prototype in the Node.js process hosting the middleware, via two unvalidated entry points that reach internal object-key writes: getResourcesHandler and missingKeyHandler. This can break authorisation checks (if (user.isAdmin) returning true for any user), cause type-confusion DoS, and depending on downstream code it can be chained into RCE.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
High
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 24% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
I1
i18next-http-middleware · i18next
< 3.9.3 · source: vendor
Affected product
I1
i18next-http-middleware
i18next
More from i18next-http-middleware
9.1
CVE-2026-48714
i18next-http-middleware missingKeyHandler does not reject keys whose segments contain prototype-polluting names
8.6
CVE-2026-41683
HTTP response splitting and DoS in i18next-http-middleware via unsanitised Content-Language header
8.2
CVE-2026-42353
Path traversal / SSRF in i18next-http-middleware via user-controlled language and namespace parameters