← Back
CVE-2026-55451
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-1321) exists in gettext-converter. Attackers reach the vulnerable code path via ``__proto__`` without authentication.
📍 Affected scope
gettext-converter — . Attack surface: `__proto__` / `Object.prototype` / `constructor` / `prototype`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.3.3**.
🛡️ Workaround
Workaround: Upgrade to `1.3.3`.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Upgrade to `1.3.3`.パッチが適用されるまでの応急処置として、Upgrade to `1.3.3`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade gettext-converter to 1.3.3ステージング環境で 1.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
gettext-converter
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.3"}]}]
References
- web https://github.com/locize/gettext-converter/security/advisories/GHSA-f4jp-rw7w-ccwg
- web https://github.com/locize/gettext-converter/issues/15
- web https://github.com/locize/gettext-converter/commit/df90c3b93e51faef68891d97b626544f619c5b31
- web https://github.com/locize/gettext-converter/releases/tag/v1.3.3
- web https://github.com/advisories/GHSA-f4jp-rw7w-ccwg