CVE-2026-104846

Published: Ott 02, 2026 Last Modified: Ott 02, 2026
ExploitDB:
Other exploit source:
Google Dorks:
CRITICAL 9,8
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Scope: unchanged
Confidentiality: high
Integrity: high
Availability: high

Description

AI Translation Available

Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. From 0.12.0 until 1.6.2, fromJSON deserialization of a fulfilled Promise control node can pass a plugin-produced callable-bearing thenable to a native Promise resolver. ECMAScript thenable assimilation then invokes the callable unexpectedly, allowing attacker-controlled JSON to trigger code in applications using plugin-capable Seroval releases. This path bypasses the Promise resolver type-confusion remediation in version 1.5.3 for CVE-2026-59940 because the unexpected invocation occurs through native Promise settlement after the referenced value is deserialized. This issue is fixed in version 1.6.2.

843

Access of Resource Using Incompatible Type ('Type Confusion')

Incomplete
Common Consequences
Security Scopes Affected:
Availability Integrity Confidentiality
Potential Impacts:
Read Memory Modify Memory Execute Unauthorized Code Or Commands Dos: Crash, Exit, Or Restart
Applicable Platforms
Languages: C, C++
View CWE Details
https://github.com/lxsmnsyc/seroval/commit/f1ffcc96d259f9b5b3d71feb262b58240c90…
https://github.com/lxsmnsyc/seroval/security/advisories/GHSA-p6vx-979v-rg4c