CVE-2026-59940

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 18, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
Patch available. Sources: github.
github Patch Available

`seroval.fromJSON()` Promise resolver type confusion invokes attacker-controlled methods during deserialization · Advisory · lxsmnsyc/seroval · GitHub

https://github.com/lxsmnsyc/seroval/security/advisories/GHSA-mv8w-475r-vwqw

Vendor Advisories for CVE-2026-59940(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
seroval1.5.3

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 16:09 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 18:05 UTCEG score recompute
  4. 2026-08-24 12:17 UTCEG score recompute
  5. 2026-08-23 04:22 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 01:50 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 23:17 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 20:18 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 16:49 UTCEG score recompute
  14. 2026-08-18 16:00 UTCEG score recompute
  15. 2026-08-18 15:34 UTCEG score recompute
  16. 2026-07-30 12:00 UTCEG score recompute
  17. 2026-07-26 14:13 UTCEG score recompute
  18. 2026-07-24 17:13 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-59940?
CVE-2026-59940 is a critical vulnerability published on July 24, 2026. 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…
When was CVE-2026-59940 disclosed?
CVE-2026-59940 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59940 actively exploited?
CVE-2026-59940 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.2% of all scored CVEs.
What is the CVSS score of CVE-2026-59940?
CVE-2026-59940 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-59940?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59940, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59940

Explore →

Is Your Infrastructure Affected by CVE-2026-59940?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.