CVE-2026-90559
Description
A flaw was found in snappy-java. This out-of-bounds write vulnerability occurs in the Snappy.uncompress function when the destination buffer's capacity is not validated against the decompressed size. A remote attacker can supply valid compressed data that, when decompressed, exceeds the buffer's boundaries. This can lead to writes past buffer boundaries, resulting in a Denial of Service (DoS) by terminating the Java Virtual Machine (JVM).
Statement
A flaw in org.xerial/snappy-java allows an unauthenticated remote attacker to crash an application JVM when attacker-controlled compressed data is passed to Snappy.uncompress(ByteBuffer, ByteBuffer) with an undersized destination buffer. The native decompression path can write beyond the supplied buffer and terminate the JVM. SELinux, non-root execution, and container boundaries limit host impact but do not prevent the application-level denial of service.
Mitigation
Reject untrusted compressed input or enforce a verified maximum decompressed size before invoking the ByteBuffer decompression API.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | 7.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
