Parsing-thread crash via unchecked serialized length fields
Published Sep 10, 2026 · Updated Sep 10, 2026
Denial of service in t-digest 3.1 through 3.3 allows remote attackers to abort parsing threads via crafted serialized digests. MergingDigest.fromBytes uses attacker-controlled compression, n, bufferSize, and lastUsedCell values as allocation sizes and loop bounds without validating capacity or remaining input. A malformed digest must reach an application's deserialization path; the resulting Java exceptions can stop a thread, worker, or ingestion job without code execution or data access.
Summary
What happened
Denial of service in t-digest 3.1 through 3.3 allows remote attackers to abort parsing threads via crafted serialized digests. MergingDigest.fromBytes uses attacker-controlled compression, n, bufferSize, and lastUsedCell values as allocation sizes and loop bounds without validating capacity or remaining input. A malformed digest must reach an application's deserialization path; the resulting Java exceptions can stop a thread, worker, or ingestion job without code execution or data access.
The record
- CVE
- CVE-2026-87962
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Ted Dunning
- Product
- t-digest
- Classifications
- CWE-1284, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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=3.1 <=3.3
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
- Crafted ByteBuffer crash proofs 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