Memory corruption via unchecked shared-pointer aliasing
Published May 26, 2026 · Updated May 26, 2026
Improper type validation in Bitsery 5.2.0 through 5.2.4 allows remote attackers to corrupt application memory via crafted serialized data. The shared-pointer deserialization path reuses a pointer ID and aliases the stored object through reinterpret_cast without confirming type compatibility. An embedding application must deserialize attacker-controlled data with pointer extensions; a mismatch produces invalid memory access or a crash.
Summary
What happened
Improper type validation in Bitsery 5.2.0 through 5.2.4 allows remote attackers to corrupt application memory via crafted serialized data. The shared-pointer deserialization path reuses a pointer ID and aliases the stored object through reinterpret_cast without confirming type compatibility. An embedding application must deserialize attacker-controlled data with pointer extensions; a mismatch produces invalid memory access or a crash.
The record
- CVE
- CVE-2026-9521
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- fraillt
- Product
- Bitsery
- Classifications
- CWE-20, CWE-1287
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 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=5.2.0
- Affected versionversion=5.2.1
- Affected versionversion=5.2.2
- Affected versionversion=5.2.3
- Affected versionversion=5.2.4
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
- Bitsery 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