seroval
Affected
- introduced
0, fixed1.5.3(semver)
Fixed versions
1.5.3
Fix
- Fixed version
1.5.3npm install [email protected]
Advisory
Also known as: CVE-2026-59940
seroval: seroval.fromJSON() Promise resolver type confusion invokes attacker-controlled methods during deserialization
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
serovalfromJSON()1.5.3 that contain the vulnerable Promise resolver reference handling1.5.3Impact
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:
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.[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.
Critical Basis: The source's own band: CRITICAL
0, fixed 1.5.3 (semver)1.5.3
1.5.3npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0