JVM termination via unchecked destination capacity
Published Sep 17, 2026 · Updated Sep 17, 2026
Out-of-bounds write in Xerial snappy-java 1.1.10.8 and earlier allows remote attackers to terminate the JVM via incompressible input. Snappy.compress(ByteBuffer, ByteBuffer) invokes native RawCompress without checking the destination buffer against maxCompressedLength, so output crosses its remaining capacity. Exploitation requires an application to compress attacker-influenced data into an undersized destination ByteBuffer; the demonstrated consequence is off-heap corruption and JVM termination.
Summary
What happened
Out-of-bounds write in Xerial snappy-java 1.1.10.8 and earlier allows remote attackers to terminate the JVM via incompressible input. Snappy.compress(ByteBuffer, ByteBuffer) invokes native RawCompress without checking the destination buffer against maxCompressedLength, so output crosses its remaining capacity. Exploitation requires an application to compress attacker-influenced data into an undersized destination ByteBuffer; the demonstrated consequence is off-heap corruption and JVM termination.
The record
- CVE
- CVE-2026-93452
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Xerial
- Product
- snappy-java
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=0 <=1.1.10.8
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- snappy-java Issue 732 reproductionproof 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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started