Prototype pollution via unchecked assign path
Published Oct 1, 2024 · Updated Aug 16, 2026
Prototype pollution in uPlot before 1.6.31 allows attackers to tamper with application object state via crafted property paths. The uplot.assign function walks attacker-controlled attribute paths and writes nested properties without rejecting a path segment that resolves to Object.prototype. Exposure depends on application code passing untrusted keys into assign; when reachable, polluted defaults can corrupt downstream logic and cause integrity loss with limited availability impact.
Summary
What happened
Prototype pollution in uPlot before 1.6.31 allows attackers to tamper with application object state via crafted property paths. The uplot.assign function walks attacker-controlled attribute paths and writes nested properties without rejecting a path segment that resolves to Object.prototype. Exposure depends on application code passing untrusted keys into assign; when reachable, polluted defaults can corrupt downstream logic and cause integrity loss with limited availability impact.
The record
- CVE
- CVE-2024-21489
- Published
- Oct 1, 2024
- Updated
- Aug 16, 2026
- Vendor
- leeoniya
- Product
- uPlot
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.31
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo