CVE-2026-59940: lxsmnsyc seroval · Deserialization of Untrusted Data
Affects lxsmnsyc serovalSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.5.3 as a priority.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade seroval and lxsmnsyc/seroval to 1.5.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| lxsmnsycseroval | Affected
| Fixed in
|
GitHublxsmnsyc/serovalpkg:github/lxsmnsyc/serovalOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in seroval version 1.5.3. Users should upgrade to version 1.5.3 or later to remediate this issue. No other official remediation or temporary fixes are indicated. Patch status is not explicitly confirmed in vendor advisories but the description states the issue is fixed in 1.5.3.
Description
Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.5.3, seroval.fromJSON() allows attacker-controlled JSON Promise control nodes to operate on values from the general deserialization reference table without verifying genuine internal Promise resolver records, causing deserialization side effects with plugins enabled and potentially unintended server-side invocation or remote code execution when downstream frameworks register callable wrappers. This issue is fixed in version 1.5.3.