CVE-2026-48714: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in i18next i18next-http-middleware
A prototype pollution vulnerability exists in i18next-http-middleware versions prior to 3.9.7. The middleware's missingKeyHandler blocks literal keys like __proto__, constructor, and prototype but does not block dotted variants such as "__proto__.polluted". When used with downstream backends like i18next-fs-backend ≤ 2.6.5 that split keys on a configured separator and write to Object.prototype without proper guards, this can lead to remote prototype pollution. This may cause crashes, corrupted translation behavior, configuration poisoning, or bypasses of property-based security checks. The issue is fixed in version 3.9.7.
AI Analysis
Technical Summary
The i18next-http-middleware package for Node.js and Deno prior to version 3.9.7 contains a prototype pollution vulnerability (CWE-1321) in its missingKeyHandler. Although literal keys __proto__, constructor, and prototype are blocked since version 3.9.3, dotted variants such as "__proto__.polluted" are not rejected. Downstream backends like i18next-fs-backend ≤ 2.6.5 that split the missing key string on a configured keySeparator and use an unguarded setPath() function to write to Object.prototype are vulnerable to remote prototype pollution. This vulnerability can be exploited if the application exposes missingKeyHandler to untrusted input and uses affected downstream backends. The impact includes potential application crashes, corrupted translation data, configuration poisoning, or security bypasses. The vulnerability is fixed in i18next-http-middleware version 3.9.7.
Potential Impact
Exploitation allows remote attackers to perform prototype pollution via crafted missing-key strings containing dotted variants of __proto__, constructor, or prototype. This can lead to application crashes, corrupted translation behavior, configuration poisoning, or bypass of property-based security controls depending on the host application and backend usage. There is no confidentiality impact reported. The CVSS v3.1 score is 9.1 (critical) with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on integrity and availability.
Mitigation Recommendations
A fixed version 3.9.7 of i18next-http-middleware is available and should be applied to remediate this vulnerability. If immediate upgrade is not possible, developers should ensure missingKeyHandler is not exposed to untrusted users by mounting it behind authentication or removing the route. Additionally, implement a request-body filter that rejects any top-level keys containing __proto__, constructor, or prototype after splitting on the configured keySeparator. Also, disable missing-key persistence by setting saveMissing to false when accepting writes from untrusted input. These mitigations reduce exposure until the official fix can be applied.
CVE-2026-48714: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in i18next i18next-http-middleware
Description
A prototype pollution vulnerability exists in i18next-http-middleware versions prior to 3.9.7. The middleware's missingKeyHandler blocks literal keys like __proto__, constructor, and prototype but does not block dotted variants such as "__proto__.polluted". When used with downstream backends like i18next-fs-backend ≤ 2.6.5 that split keys on a configured separator and write to Object.prototype without proper guards, this can lead to remote prototype pollution. This may cause crashes, corrupted translation behavior, configuration poisoning, or bypasses of property-based security checks. The issue is fixed in version 3.9.7.
CVSS v3.1
Score 9.1critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The i18next-http-middleware package for Node.js and Deno prior to version 3.9.7 contains a prototype pollution vulnerability (CWE-1321) in its missingKeyHandler. Although literal keys __proto__, constructor, and prototype are blocked since version 3.9.3, dotted variants such as "__proto__.polluted" are not rejected. Downstream backends like i18next-fs-backend ≤ 2.6.5 that split the missing key string on a configured keySeparator and use an unguarded setPath() function to write to Object.prototype are vulnerable to remote prototype pollution. This vulnerability can be exploited if the application exposes missingKeyHandler to untrusted input and uses affected downstream backends. The impact includes potential application crashes, corrupted translation data, configuration poisoning, or security bypasses. The vulnerability is fixed in i18next-http-middleware version 3.9.7.
Potential Impact
Exploitation allows remote attackers to perform prototype pollution via crafted missing-key strings containing dotted variants of __proto__, constructor, or prototype. This can lead to application crashes, corrupted translation behavior, configuration poisoning, or bypass of property-based security controls depending on the host application and backend usage. There is no confidentiality impact reported. The CVSS v3.1 score is 9.1 (critical) with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on integrity and availability.
Mitigation Recommendations
A fixed version 3.9.7 of i18next-http-middleware is available and should be applied to remediate this vulnerability. If immediate upgrade is not possible, developers should ensure missingKeyHandler is not exposed to untrusted users by mounting it behind authentication or removing the route. Additionally, implement a request-body filter that rejects any top-level keys containing __proto__, constructor, or prototype after splitting on the configured keySeparator. Also, disable missing-key persistence by setting saveMissing to false when accepting writes from untrusted input. These mitigations reduce exposure until the official fix can be applied.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-22T18:47:27.755Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a30726b0b89be6888a31ae3
Added to database: 06/15/2026, 21:45:15 UTC
Last enriched: 06/23/2026, 15:32:03 UTC
Last updated: 08/01/2026, 07:18:00 UTC
Views: 110
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.