CVE-2026-102554

Denial of Service via Eager Array Allocation During Deserialization in Guava

Published Oct 9, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
Allocation of resources without limits or throttling (CWE-770) during Java object deserialization in Google Guava versions 4.0 through 33.7.1 allows an attacker to cause a Denial of Service via OutOfMemoryError. When deserializing CompactHashMap, CompactHashSet, or MapMakerInternalMap instances, Guava eagerly allocates an array based on a caller-specified size parameter without throttling, permitting memory exhaustion from crafted serialization streams.

Analysis

AI-generated

Technical impact

A crafted serialization stream can cause Guava’s CompactHashMap, CompactHashSet, or MapMakerInternalMap to eagerly allocate an array sized from the input without any limits or throttling. The resulting allocation can exhaust heap memory, raise an OutOfMemoryError, and bring the application or process down. This flaw is a deserialization weakness (CWE‑502) coupled with uncontrolled resource consumption (CWE‑770), and its primary impact is denial of service.

Affected Systems

Google Guava Java library, versions 4.0 through 33.7.1. Any Java application that deserializes CompactHashMap, CompactHashSet, or MapMakerInternalMap objects from untrusted data is vulnerable.

Risk and Exploitability

The CVSS score of 8.2 reflects high severity, and although the EPSS score is not available, the lack of input size limits makes exploitation straightforward. The vulnerability is not listed in CISA KEV, meaning no publicly known exploits exist yet, but attackers can target applications that perform deserialization of Guava objects. No special privileges are needed beyond delivering a malicious serialized payload.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Guava version 33.7.2 or later.
  • Validate the size of array parameters before deserializing Guava objects, enforcing a maximum limit to prevent large allocations.
  • Configure JVM heap size limits and monitor for OutOfMemoryError events, triggering alerts and graceful shutdowns to mitigate disruption.
  • If upgrade is delayed, consider disabling Guava deserialization features in untrusted contexts.

Generated by OpenCVE AI on October 9, 2026 at 16:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-xxph-c9ww-hj94 Google Guava: CompactHashMap/CompactHashSet/MapMakerInternalMap deserialization triggers uncontrolled memory allocation
History
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Google
Google guava
Vendors & Products Google
Google guava
Type Values Removed Values Added
Description Allocation of resources without limits or throttling (CWE-770) during Java object deserialization in Google Guava versions 4.0 through 33.7.1 allows an attacker to cause a Denial of Service via OutOfMemoryError. When deserializing CompactHashMap, CompactHashSet, or MapMakerInternalMap instances, Guava eagerly allocates an array based on a caller-specified size parameter without throttling, permitting memory exhaustion from crafted serialization streams.
Title Denial of Service via Eager Array Allocation During Deserialization in Guava
Weaknesses CWE-502
CWE-770
References
Metrics cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
Google
Published
Updated
Oct 9, 2026, 6:09 PM
Reserved
Sep 29, 2026, 1:06 PM
Status
Awaiting Analysis
Published
Oct 9, 2026, 4:17 PM
Modified
Oct 9, 2026, 6:17 PM
Severity
Important
Public date
Oct 9, 2026, 3:07 PM