CVE-2024-21528 — node-gettext
MEDIUMCVE-2024-21528 is a medium-severity (CVSS 5.9) CWE-1321 vulnerability in node-gettext. No vendor fix is recorded yet; mitigation options are listed below.
node-gettext vulnerable to Prototype Pollution
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-21528.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-21528 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
node-gettextnpmDescription
All versions of the package node-gettext are vulnerable to Prototype Pollution via the addTranslations() function in gettext.js due to improper user input sanitization.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | node-gettext | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-gettext, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of node-gettext has shipped for CVE-2024-21528 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-21528 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-21528. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| RHODF-4.15-RHEL-9 | odf4/odf-console-rhel9:v4.15.12-1 | RHSA-2025:1865 |
| RHODF-4.16-RHEL-9 | odf4/ocs-client-console-rhel9:v4.16.8-1 | RHSA-2025:1829 |
| RHODF-4.17-RHEL-9 | odf4/odf-console-rhel9:v4.17.5-1 | RHSA-2025:1824 |
| RHODF-4.18-RHEL-9 | odf4/ocs-client-console-rhel9:v4.18.0-65 | RHSA-2025:2652 |
Frequently Asked Questions
Is CVE-2024-21528 in your dependencies?
O3 Security finds CVE-2024-21528 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.