Google Guava is a widely used Java library; deserialization-induced memory exhaustion can disrupt many enterprise apps and services.
CVE-2026-102554
Guava deserialization flaw allows memory-exhausting DoS.
Is CVE-2026-102554 being exploited?
Not confirmed. CVE-2026-102554 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-102554?
CVE-2026-102554 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-102554?
Yes. A fix has been recorded for CVE-2026-102554. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-102554 affect?
CVE-2026-102554 affects Google Guava versions 4.0 through 33.7.1, Java applications using Guava CompactHashMap/CompactHashSet/MapMakerInternalMap, Any service accepting untrusted Java serialized streams. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-102554?
Upgrade Guava to >=33.7.2 and block/validate untrusted Java deserialization
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted serialized streams trigger eager allocation during CompactHashMap/CompactHashSet/MapMakerInternalMap deserialization, causing OutOfMemoryError and remote Denial of Service.
Patch when possible
- affected>= 4.0 and < 33.7.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.