Vulnerability in gettext-converter (CVE-2026-55451)
Summary
Vulnerability in gettext-converter (CVE-2026-55451). Risk of unauthorized operations or information disclosure. Exploitable via __proto__. Mitigation: upgrade to 1.3.3 or later.
Original description
The description as published by the source.
Impact
js2i18next() is vulnerable to prototype pollution. When converting translations, it splits nested keys on the key separator (default ##) and uses each segment as a dynamic object key while building the output object. A key whose segment is __proto__ (e.g. __proto__##gcPolluted) causes the converter to resolve Object.prototype as the nested write target and assign the translated value onto it, polluting Object.prototype for the whole runtime.
Any application that converts translation data (PO / i18next JS objects) originating from an untrusted or user-controlled source is affected. Prototype pollution can lead to denial of service and, depending on the surrounding application, may enable further attacks.
Patches
Fixed in gettext-converter@1.3.3. Key segments equal to __proto__, constructor, or prototype are now rejected before being used as dynamic object keys.
Workarounds
Upgrade to 1.3.3. If upgrading is not immediately possible, sanitize/validate translation keys before passing them to js2i18next() and reject any key whose ##-separated segments include __proto__, constructor, or prototype.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55451 has been found in gettext-converter.
Attackers can target a specific entry point like __proto__ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade gettext-converter to 1.3.3 or later.
If unsure, ask your IT team or search "gettext-converter CVE-2026-55451" on the vendor's site.
CVE-2026-55451 (gettext-converter) — CWE-1321
Attack surface: __proto__ / Object.prototype / constructor / prototype
Patched: 1.3.3 — apply immediately
Workaround: Upgrade to 1.3.3.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in gettext-converter. Attackers reach the vulnerable code path via __proto__.
Check the vendor advisory for the affected versions of gettext-converter. Attack surface: __proto__ / Object.prototype / constructor / prototype.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.3.3.
Workaround: Upgrade to 1.3.3.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gettext-converter' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gettext-converter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gettext-converterを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Upgrade to `1.3.3`.パッチが適用されるまでの応急処置として、Upgrade to
1.3.3. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade gettext-converter to 1.3.3ステージング環境で 1.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com