Vulnerability Description
gettext-converter provides gettext resource conversion utilities for JavaScript. Prior to 1.3.3, js2i18next() in lib/js2i18next.js splits nested translation keys using options.keyseparator, whose default value consists of two number signs, and uses each segment as a dynamic object key without rejecting __proto__, constructor, or prototype. When an application converts untrusted PO or i18next translation data, a __proto__ segment resolves Object.prototype as the nested write target and Object.assign writes attacker-controlled translated properties onto the process-wide prototype. The resulting prototype pollution can cause denial of service and may enable application-dependent follow-on attacks. This issue is fixed in version 1.3.3.
Related Weaknesses (CWE)
References
- https://github.com/locize/gettext-converter/commit/df90c3b93e51faef68891d97b6265
- https://github.com/locize/gettext-converter/issues/15
- https://github.com/locize/gettext-converter/releases/tag/v1.3.3
- https://github.com/locize/gettext-converter/security/advisories/GHSA-f4jp-rw7w-c
- https://github.com/locize/gettext-converter/issues/15
FAQ
What is CVE-2026-55451?
CVE-2026-55451 is a documented vulnerability. gettext-converter provides gettext resource conversion utilities for JavaScript. Prior to 1.3.3, js2i18next() in lib/js2i18next.js splits nested translation keys using options.keyseparator, whose defa...
How severe is CVE-2026-55451?
CVSS scoring is not yet available for CVE-2026-55451. Check NVD for updates.
Is there a patch for CVE-2026-55451?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.