Advisory record · GHSA-55g7-9cwv-5qfv

snappy-java's missing upper bound check on chunk length can lead to Denial of Service (DoS) impact

CVSS 7.5 HighEPSS 0.012 · 68th percentile

Published by the GitHub Advisory Database at 25 Sept 2023, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.xerial.snappy:snappy-javaMaven<1.1.10.41.1.10.4
Identifiers
GHSA-55g7-9cwv-5qfv · CVE-2023-43642
Weakness (CWE)
CWE-770
Published
25 Sept 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

snappy-java versions before 1.1.10.4 are vulnerable to denial of service when SnappyInputStream decompresses data with a very large chunk size, because the chunk length has no upper bound check. An attacker who can supply compressed data to an application that decompresses it with this library can make the application attempt a huge heap allocation, causing an OutOfMemoryError that may crash it. Upgrade to snappy-java 1.1.10.4 or later.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.012, the 68th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:18 UTC First seen by agentprime
  2. 31 Oct 2026, 14:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.