CVE-2026-123561
Received Received - Intake

devalue before 5.9.3 Prototype Pollution via Malformed Keys

Vulnerability report for CVE-2026-123561, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-08

Last updated on: 2026-11-08

Assigner: VulnCheck

Description

devalue before 5.9.3 allows malformed null-prototype object keys to bypass parse's __proto__ rejection through property-key coercion, an incomplete fix for GHSA-mwv9-gp5h-frr4. Attackers can supply crafted payloads that yield objects with a __proto__ own property, which alone does not cause prototype pollution.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-08
Last Modified
2026-11-08
Generated
2026-11-08
AI Q&A
2026-11-08
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1321 The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the devalue npm package before version 5.9.3. It allows attackers to bypass the parse function's rejection of __proto__ properties by using malformed null-prototype object keys through property-key coercion. This creates objects with a __proto__ own property but does not directly cause prototype pollution.

Detection Guidance

Check the installed version of the devalue package using npm list devalue or npm list -g devalue. If the version is below 5.9.3, the system is vulnerable. Review application code that uses devalue for parsing user input, especially where object keys are processed.

Impact Analysis

The impact is limited as the vulnerability does not directly cause prototype pollution. However, it could potentially allow attackers to manipulate object prototypes in unexpected ways, which might lead to secondary issues depending on the application's use of devalue.

Mitigation Strategies

Upgrade the devalue package to version 5.9.3 or later using npm update devalue or npm install devalue@latest. If upgrading is not immediately possible, review and sanitize all user-supplied input before passing it to devalue's parse function.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-123561. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...