CVE-2026-102554: Denial of Service via Eager Array Allocation During Deserialization in Guava
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by Google, published 2026-10-09).
Weakness: CWE-770 Allocation of Resources Without Limits or Throttling; CWE-502 Deserialization of Untrusted Data
How it can be exploited
Exploitable over the network with low attack complexity only when specific conditions are present needing no privileges and no user interaction. Impact: confidentiality none, integrity none, availability high. 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
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.972
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Google Guava | from 4.0 before 33.7.2 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 33.7.2.
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Other references
- https://github.com/google/guava/security/advisories/GHSA-xxph-c9ww-hj94
- https://github.com/google/guava/commit/b931fe9d6d5cf00bc55714ad3308d086f71850fe
- https://github.com/google/guava/releases/tag/v33.7.2
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
