seroval is vulnerable to Type Confusion
98
CVE Score
Critical
Type Confusion
seroval's fromJSON() resolves and rejects deserialized Promise nodes by passing the raw decoded value to the promise's resolver, without checking whether that value is itself a thenable. A plugin produced object with a then method reaches this path, so native Promise mechanics invoke it automatically once the payload settles the promise, letting the deserialized data trigger an unintended callable. This bypasses the earlier type-confusion guard added for the same class of issue and reaches every plugin capable release. The fix rejects any deserialized value exposing a then function before it can settle a promise.
Upgrade the seroval library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you use a seroval plugin that can produce a callable value.
0.12.0 - 1.6.1
Fixed in 1.6.2seroval is vulnerable to Type Confusion in versions 0.12.0 - 1.6.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.