Answer in brief
CVE-2026-55451 records a Medium severity (CVSS 8.3) vulnerability in gettext-converter: Prototype pollution in js2i18next() via crafted translation keys. The current sources do not mark it as known exploited. The current feed maps locize/gettext-converter (generic), gettext-converter (npm), gettext-converter (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps locize/gettext-converter (generic), gettext-converter (npm), gettext-converter (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| locize/gettext-convertergeneric | <1.3.3 | 1.3.3 |
| gettext-converternpm | <1.3.3 | 1.3.3 |
| gettext-converternpm | >=0 <1.3.3 | 1.3.3 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.