How severe is GHSA-f4jp-rw7w-ccwg?

No CVSS score has been assigned to GHSA-f4jp-rw7w-ccwg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f4jp-rw7w-ccwg?

GHSA-f4jp-rw7w-ccwg affects the following packages: gettext-converter (npm). Ecosystems affected: npm.

How do I fix GHSA-f4jp-rw7w-ccwg?

Update gettext-converter to 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4jp-rw7w-ccwg is resolved across your whole dependency graph.

How do I detect GHSA-f4jp-rw7w-ccwg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gettext-converter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-f4jp-rw7w-ccwg if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-f4jp-rw7w-ccwg actively exploited in the wild?

No public exploit code has been indexed for GHSA-f4jp-rw7w-ccwg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-f4jp-rw7w-ccwg?

GHSA-f4jp-rw7w-ccwg has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-f4jp-rw7w-ccwg?

GHSA-f4jp-rw7w-ccwg is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f4jp-rw7w-ccwg published, and has it been updated?

GHSA-f4jp-rw7w-ccwg was published on August 20, 2026 and was last updated on August 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-f4jp-rw7w-ccwg — gettext-converter

Fix: locize/gettext-converter@df90c3b

GHSA-f4jp-rw7w-ccwg is a CWE-1321 vulnerability in gettext-converter. A fix is available for gettext-converter — see the affected versions and patch details below.

gettext-converter: Prototype pollution in js2i18next() via crafted translation keys

Also known asCVE-2026-55451

Published

Aug 20, 2026

Updated

Aug 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-f4jp-rw7w-ccwg.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

gettext-converternpm

90Kdownloads / week

Description

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 [email protected]. 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`gettext-converter`	all versions	1.3.3`npm install gettext-converter@1.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gettext-converter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gettext-converter to 1.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4jp-rw7w-ccwg is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-f4jp-rw7w-ccwg in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works