How severe is CVE-2024-21489?

No CVSS score has been assigned to CVE-2024-21489 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-21489?

CVE-2024-21489 affects the following packages: uplot (npm). Ecosystems affected: npm.

How do I fix CVE-2024-21489?

Update uplot to 1.6.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-21489 is resolved across your whole dependency graph.

How do I detect CVE-2024-21489 in my npm dependencies?

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

How do I mitigate CVE-2024-21489 if there is no patch (or I can't update yet)?

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.

Is CVE-2024-21489 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-21489 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 CVE-2024-21489?

CVE-2024-21489 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 54th 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 CVE-2024-21489?

CVE-2024-21489 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 CVE-2024-21489 published, and has it been updated?

CVE-2024-21489 was published on October 1, 2024 and was last updated on October 28, 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

CVE-2024-21489 — uplot

Fix: leeoniya/uPlot@5756e3e

CVE-2024-21489 is a CWE-1321 vulnerability in uplot. A fix is available for uplot — see the affected versions and patch details below.

uPlot Prototype Pollution vulnerability

Also known asGHSA-34q8-jcq6-mc37

Published

Oct 1, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 4, 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 CVE-2024-21489.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% 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.

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

uplotnpm

1.0Mdownloads / week

Description

Versions of the package uplot before 1.6.31 are vulnerable to Prototype Pollution via the uplot.assign function due to missing check if the attribute resolves to the object prototype.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`uplot`	all versions	1.6.31`npm install uplot@1.6.31`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uplot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update uplot to 1.6.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-21489 is resolved across your whole dependency graph.
Workarounds
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 HatImportant

Grafana is not impacted by this CVE, as the vulnerable `uplot.assign` function is not utilized in Grafana on Red Hat Enterprise Linux. Only RHEL-8.4.z having the issue.

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-21489 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support	`grafana-0:7.3.6-7.el8_4`	RHSA-2024:8083

Frequently Asked Questions

Versions of the package uplot before 1.6.31 are vulnerable to Prototype Pollution via the uplot.assign function due to missing check if the attribute resolves to the object prototype.

O3 Security · Impact-Aware SCA

Is CVE-2024-21489 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works