NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2024-21528 — node-gettext

MEDIUM

CVE-2024-21528 is a medium-severity (CVSS 5.9) CWE-1321 vulnerability in node-gettext. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

node-gettext vulnerable to Prototype Pollution

Published
Updated
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk
0.00%0.36%0.71%1.07%0.1%0.6%Jun 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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.

51other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
node-gettextnpm
78Kdownloads / week

Description

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

1 total
EcosystemPackageVulnerable rangeFix
📦npmnode-gettextall versionsNo fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Remediation status

    The records we use list no patched version of node-gettext for CVE-2024-21528. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. 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.

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.

Red HatModerate
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-21528 (CC BY 4.0)
ProductFixed inAdvisory
RHODF-4.15-RHEL-9odf4/odf-console-rhel9:v4.15.12-1RHSA-2025:1865
RHODF-4.16-RHEL-9odf4/ocs-client-console-rhel9:v4.16.8-1RHSA-2025:1829
RHODF-4.17-RHEL-9odf4/odf-console-rhel9:v4.17.5-1RHSA-2025:1824
RHODF-4.18-RHEL-9odf4/ocs-client-console-rhel9:v4.18.0-65RHSA-2025:2652

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-21528 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-21528: node-gettext (Medium 5.9)