CVE-2026-23736
Lxsmnsyc Seroval ≤ 1.4.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-23736 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Lxsmnsyc Seroval. Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-23736 is a vulnerability in the seroval JavaScript library, which enables stringification of JavaScript values including complex structures beyond standard JSON.stringify capabilities. In versions 1.4.0 and below, improper input validation allows a malicious object key to cause prototype pollution during JSON deserialization. This issue is limited to the JSON deserialization functionality and is associated with CWE-1321. The vulnerability received a CVSS v3.1 base score of 7.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) and was published on 2026-01-21.
A remote, unauthenticated attacker can exploit this vulnerability by supplying malicious input to an affected seroval JSON deserialization operation. Successful exploitation leads to prototype pollution, where the attacker can modify properties on Object.prototype, potentially enabling further attacks such as denial of service, information disclosure, or code execution depending on the application's use of polluted prototypes. The low complexity and lack of privileges required make it accessible to attackers targeting applications that process untrusted JSON inputs with vulnerable seroval versions.
The seroval security advisory (GHSA-hj76-42vx-jwp4) and corresponding commit (ce9408ebc87312fcad345a73c172212f2a798060) confirm the issue is fixed in version 1.4.1 through improved input validation. Security practitioners should upgrade to seroval 1.4.1 or later and review applications for unsafe deserialization of untrusted JSON inputs using this library.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3680
Vulnerability Data
seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, due to improper input validation, a malicious object key can lead to prototype pollution during JSON deserialization. This vulnerability affects only JSON deserialization functionality.…
more
This issue is fixed in version 1.4.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.3.6
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches prototype-pollution flaws before release.
Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.
Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.