Denial of service via prototype pollution
Published Sep 14, 2026 · Updated Sep 14, 2026
Prototype pollution in Locize gettext-converter before 1.3.3 allows remote attackers to alter Object.prototype via crafted translation keys. The js2i18next() function splits keys on options.keyseparator and uses unchecked proto, constructor, or prototype segments as dynamic Object.assign targets. Exposure requires attacker-controlled PO or i18next data to reach conversion; process-wide pollution can cause denial of service or application-dependent attacks.
Summary
What happened
Prototype pollution in Locize gettext-converter before 1.3.3 allows remote attackers to alter Object.prototype via crafted translation keys. The js2i18next() function splits keys on options.keyseparator and uses unchecked proto, constructor, or prototype segments as dynamic Object.assign targets. Exposure requires attacker-controlled PO or i18next data to reach conversion; process-wide pollution can cause denial of service or application-dependent attacks.
The record
- CVE
- CVE-2026-55451
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Locize
- Product
- gettext-converter
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Minimal js2i18next prototype-pollution reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo