Is org.xerial.snappy:snappy-java 1.0 vulnerable?
Maven · 11 releases from 1.0.3 to 1.0.5.4 · latest org.xerial.snappy:snappy-java is 1.1.10.12 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. org.xerial.snappy:snappy-java 1.0.5.4, the last 1.0 release, is affected by 7 known security advisories (4 high, 3 medium), including CVE-2026-93451, CVE-2026-108106, CVE-2023-43642. Upgrade to 1.1.10.9 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.xerial.snappy:snappy-java -DdepVersion=1.1.10.9 -DforceVersion=trueIs your project on an affected org.xerial.snappy:snappy-java?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.xerial.snappy:snappy-java 1.0.5.4
snappy-java: Heap buffer overflow in Snappy.uncompress*Array typed-array methods
- Affected
- <1.1.10.9
- Fixed in
- 1.1.10.9
snappy-java: JVM crash from unchecked ranges in Snappy.arrayCopy and SnappyOutputStream.rawWrite
- Affected
- <1.1.10.9
- Fixed in
- 1.1.10.9
snappy-java: Unbounded memory allocation from attacker-declared uncompressed lengtha
- Affected
- <1.1.10.9
- Fixed in
- 1.1.10.9
snappy-java's missing upper bound check on chunk length can lead to Denial of Service (DoS) impact
- Affected
- <1.1.10.4
- Fixed in
- 1.1.10.4
snappy-java's unchecked chunk length leads to DoS
- Affected
- <1.1.10.1
- Fixed in
- 1.1.10.1
snappy-java's Integer Overflow vulnerability in compress leads to DoS
- Affected
- <1.1.10.1
- Fixed in
- 1.1.10.1
snappy-java's Integer Overflow vulnerability in shuffle leads to DoS
- Affected
- <1.1.10.1
- Fixed in
- 1.1.10.1
Every org.xerial.snappy:snappy-java 1.0.x release
Affected: 1.0.3 to 1.0.5.4. Latest org.xerial.snappy:snappy-java: 1.1.10.12.
| Version | Known advisories |
|---|---|
| org.xerial.snappy:snappy-java 1.0.5.4 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.5.3 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.5.2 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.5.1 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.5 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.4.1 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.4 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.3.3 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.3.2 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.3.1 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
| org.xerial.snappy:snappy-java 1.0.3 | CVE-2026-93451, CVE-2026-116590, CVE-2026-108106, CVE-2023-43642, CVE-2023-34455, CVE-2023-34454, CVE-2023-34453 |
Which of your client projects are still on org.xerial.snappy:snappy-java 1.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.xerial.snappy:snappy-java version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.xerial.snappy:snappy-java versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.