Code execution via untyped shared-pointer ID reuse
Published Jun 7, 2026 · Updated Jun 7, 2026
Type confusion in USCiLab cereal 1.3.0 through 1.3.2 allows remote attackers to corrupt memory via crafted shared-pointer archives. The input archive reuses a shared-pointer ID from its untyped map without verifying that the retrieved object matches the destination pointer type. A consuming application must deserialize attacker-controlled data containing differently typed shared pointers in sequence; the resulting alias can disclose memory or enable arbitrary code execution.
Summary
What happened
Type confusion in USCiLab cereal 1.3.0 through 1.3.2 allows remote attackers to corrupt memory via crafted shared-pointer archives. The input archive reuses a shared-pointer ID from its untyped map without verifying that the retrieved object matches the destination pointer type. A consuming application must deserialize attacker-controlled data containing differently typed shared pointers in sequence; the resulting alias can disclose memory or enable arbitrary code execution.
The record
- CVE
- CVE-2026-11463
- Published
- Jun 7, 2026
- Updated
- Jun 7, 2026
- Vendor
- USCiLab
- Product
- cereal
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 7, 2026CVE publishedPublication date reported by the CVE source.
- Jun 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.0
- Affected versionversion=1.3.1
- Affected versionversion=1.3.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- cereal shared-pointer type-confusion proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo