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.
CVE-2026-55451
This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (44th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.3
- EG Score
- 8.3HIGHmedium confidence
- EG Risk
- 68EG Risk 68/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity83% × 45%Exploitation40% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 44th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 20, 2026
Last Modified
September 30, 2026
Advisory Details (3)
Auto-updated Sep 14, 2026commit df90c3b93e51 (locize/gettext-converter)
Fix landed in locize/gettext-converter commit df90c3b93e51 — awaiting tagged release
https://github.com/locize/gettext-converter/commit/df90c3b93e51faef68891d97b626544f619c5b31Prototype pollution in `js2i18next()` via `__proto__` translation key · Issue #15 · locize/gettext-converter · GitHub
https://github.com/locize/gettext-converter/issues/15Prototype pollution in js2i18next() via crafted translation keys · Advisory · locize/gettext-converter · GitHub
https://github.com/locize/gettext-converter/security/advisories/GHSA-f4jp-rw7w-ccwgVendor Advisories for CVE-2026-55451(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gettext-converter | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 41× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-05 08:02 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 19:24 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 19:46 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 21:28 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 20:03 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 08:10 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-29 00:28 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 14:52 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-27 02:56 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 00:40 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 23:28 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 00:50 UTCEG score recompute
- 2026-09-22 02:31 UTCEG score recompute
- 2026-09-21 04:06 UTCEG score recompute
Show 17 moreShow fewer
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 18:28 UTCEG score recompute
- 2026-09-18 19:38 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 21:19 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 19:44 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:56 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 06:31 UTCEG score recompute
- 2026-09-14 19:23 UTCEG score recompute
- 2026-09-14 19:05 UTCEG score recompute
- 2026-09-14 17:55 UTCEG score recompute
- 2026-09-14 17:00 UTCEG score recompute▲ 8.30
- 2026-09-14 16:59 UTCMITRE cvelistV5CVSS v3 → 8.3 · CVSS v4 → 8.3 · severity → HIGH
- 2026-08-20 20:42 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55451?
When was CVE-2026-55451 disclosed?
Is CVE-2026-55451 actively exploited?
What is the CVSS score of CVE-2026-55451?
How do I remediate CVE-2026-55451?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55451
Is Your Infrastructure Affected by CVE-2026-55451?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.