CVE-2026-59940
CRITICALCVE-2026-59940 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in seroval. O3 Security confirms whether CVE-2026-59940 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
seroval: `seroval.fromJSON()` Promise resolver type confusion invokes attacker-controlled methods during deserialization
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-59940 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 368,634 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
serovalnpmDescription
Summary
A type confusion issue in seroval.fromJSON() allowed attacker-controlled JSON input to cause Promise control nodes to operate on values from the general deserialization reference table without first verifying that those values were genuine internal promise resolver records.
In applications that deserialize untrusted Seroval JSON with plugins enabled, this could allow attacker-controlled deserialization side effects. In downstream server frameworks that register plugins returning callable wrappers, this primitive could become unintended server-side invocation and, depending on exposed application functionality, remote code execution or equivalent server compromise.
The issue was fixed in [email protected].
Affected package
- Package:
seroval - Affected API:
fromJSON() - Affected versions: versions prior to
1.5.3that contain the vulnerable Promise resolver reference handling - Patched version:
1.5.3
Impact
The vulnerable deserialization path could confuse attacker-created values in the general reference table with Seroval's internal promise resolver records.
Direct impact in seroval is a deserialization side-effect primitive when untrusted JSON is deserialized with plugins enabled. Downstream impact depends on registered plugins and framework usage. If a downstream framework registers plugins that deserialize sensitive callable wrappers, attacker-controlled input may be able to trigger unintended server-side invocation during deserialization.
A concrete downstream impact scenario was validated privately against TanStack Start before the 1.5.3 fix. With [email protected], the downstream reproducer no longer succeeds.
Remediation
Upgrade to [email protected] or later.
Downstream projects that accept Seroval JSON from untrusted clients should also consider defense-in-depth controls:
- restrict accepted Seroval node types for client-to-server payloads;
- allowlist plugin tags for inbound deserialization;
- avoid registering plugins that produce callable or privileged values for untrusted inputs unless strictly necessary;
- add regression tests ensuring deserialization cannot cause unintended server-side invocation as a side effect.
Fix verification
The original private reproducer was verified against [email protected] and no longer reproduces against [email protected].
Validation results:
[email protected]: vulnerable behavior reproduced.[email protected]: deserialization aborts before the attacker-controlled side effect occurs.- TanStack Start downstream proof with
[email protected]: no evidence side effect is produced.
Credit
Reported by Mufeed VH from Winfunc Research.
Disclosure / coordination note
The downstream TanStack Start impact was coordinated privately. Technical exploit details and proof-of-concept reproduction material have been omitted from this advisory draft for discretion.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | seroval | all versions | 1.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for seroval. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update seroval to 1.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-59940 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-59940 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-59940. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-59940 in your dependencies?
O3 detects CVE-2026-59940 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.