CVE-2026-93452

Description

A flaw was found in snappy-java. An attacker can trigger a buffer overflow vulnerability in the Snappy.compress(ByteBuffer, ByteBuffer) function by providing specially crafted, incompressible data. This vulnerability allows the attacker to write past the end of the destination buffer, corrupting off-heap memory. The corruption ultimately leads to the termination of the Java Virtual Machine (JVM), resulting in a denial of service.

Statement

A flaw in snappy-java allows an attacker to terminate an application JVM when attacker-controlled, incompressible data is passed to Snappy.compress(ByteBuffer, ByteBuffer) with an undersized destination buffer. The native compression path can write beyond the supplied buffer and corrupt off-heap memory. SELinux, non-root execution, and container isolation may limit impact outside the application boundary but do not prevent application-level denial of service.

Mitigation

Validate destination buffer capacity against maximum theoretical compressed payload size prior to invoking Snappy.compress, or restrict untrusted compressed input vectors at network application boundaries.

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).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/A7.5
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

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

Want to get errata notifications? Sign up here.