Cross-message data disclosure via persistent shared references
Published Dec 31, 2025 · Updated Dec 31, 2025
Information disclosure in cbor2 3.0.0 through 5.7.1 allows remote attackers to read prior decoded values via crafted CBOR shared references. CBORDecoder's decode_from_bytes and stream replacement paths leave the shareables list populated after a top-level decode, so tag 29 resolves tag 28 values from an earlier message. Exposure requires decoder reuse across trust boundaries after a trusted message used value sharing; disclosure is limited to retained shareable values.
Summary
What happened
Information disclosure in cbor2 3.0.0 through 5.7.1 allows remote attackers to read prior decoded values via crafted CBOR shared references. CBORDecoder's decode_from_bytes and stream replacement paths leave the shareables list populated after a top-level decode, so tag 29 resolves tag 28 values from an earlier message. Exposure requires decoder reuse across trust boundaries after a trusted message used value sharing; disclosure is limited to retained shareable values.
The record
- CVE
- CVE-2025-68131
- Published
- Dec 31, 2025
- Updated
- Dec 31, 2025
- Vendor
- Alex Grönholm
- Product
- cbor2
- Classifications
- CWE-212
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2025CVE publishedPublication date reported by the CVE source.
- Dec 31, 2025Record 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=>= 3.0.0, < 5.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream shared-reference disclosure proof of conceptproof of concept · demonstrated
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