VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.xerial.snappy:snappy-java: vulnerability history, versions and safety

org.xerial.snappy:snappy-java is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 78 releases, from Jun 2023 to Sep 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.xerial.snappy:snappy-java vulnerabilities

Vulert verdict on org.xerial.snappy:snappy-java 1.1.10.12 i

Updated on 23 Oct 2026

Good news: 1.1.10.12, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 1.1.10.12 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.1.10.12 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.1.10.12 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 25 Sep 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 86 packages i
  • Stars 1,083 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.xerial.snappy:snappy-java, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.1.10.12 10 Oct 2026 none Apache-2.0 — Details →
1.1.10.11 05 Oct 2026 none Apache-2.0 — Details →
1.1.10.10 03 Oct 2026 none Apache-2.0 — Details →
1.1.10.9 03 Oct 2026 none Apache-2.0 — Details →
1.1.10.8 19 Jul 2025 none Apache-2.0 — Details →
1.1.10.7 10 Sep 2024 none Apache-2.0 — Details →
1.1.10.6 07 Aug 2024 none Apache-2.0 — Details →
1.1.10.5 27 Sep 2023 none Apache-2.0 — Details →
1.1.10.4 23 Sep 2023 none Apache-2.0 — Details →
1.1.10.3 21 Jul 2023 H1 Apache-2.0 Yes Details →
1.1.10.2 13 Jul 2023 H1 Apache-2.0 Yes Details →
1.1.10.1 14 Jun 2023 H1 Apache-2.0 Yes Details →
1.1.10.0 23 May 2023 H2 M2 Apache-2.0 Yes Details →
1.1.9.1 31 Jan 2023 H2 M2 Apache-2.0 Yes Details →
1.1.9.0 28 Jan 2023 H2 M2 Apache-2.0 Yes Details →
1.1.8.4 25 Jan 2021 H2 M2 Apache-2.0 Yes Details →
1.1.8.3 20 Jan 2021 H2 M2 Apache-2.0 Yes Details →
1.1.8.2 28 Nov 2020 H2 M2 Apache-2.0 Yes Details →
1.1.8.1 09 Nov 2020 H2 M2 Apache-2.0 Yes Details →
1.1.8 21 Oct 2020 H2 M2 Apache-2.0 Yes Details →
1.1.7.8 21 Oct 2020 H2 M2 Apache-2.0 Yes Details →
1.1.7.7 26 Aug 2020 H2 M2 Apache-2.0 Yes Details →
1.1.7.6 26 Jun 2020 H2 M2 Apache-2.0 Yes Details →
1.1.7.5 06 May 2020 H2 M2 Apache-2.0 Yes Details →
1.1.7.4 05 May 2020 H2 M2 Apache-2.0 Yes Details →
1.1.7.3 26 Mar 2019 H2 M2 Apache-2.0 Yes Details →
1.1.7.2 21 May 2018 H2 M2 Apache-2.0 Yes Details →
1.1.7.1 07 Dec 2017 H2 M2 Apache-2.0 Yes Details →
1.1.7 01 Dec 2017 H2 M2 Apache-2.0 Yes Details →
1.1.4 22 May 2017 H2 M2 Apache-2.0 Yes Details →
1.1.4-M3 16 Feb 2017 H2 M2 Apache-2.0 Yes Details →
1.1.4-M2 13 Feb 2017 H2 M2 Apache-2.0 Yes Details →
1.1.4-M1 11 Feb 2017 H2 M2 Apache-2.0 Yes Details →
1.1.3-M2 26 Jan 2017 H2 M2 Apache-2.0 Yes Details →
1.1.3-M1 20 Jan 2017 H2 M2 Apache-2.0 Yes Details →
1.1.2.6 02 Jun 2016 H2 M2 Apache-2.0 Yes Details →
1.1.2.5 02 Jun 2016 H2 M2 Apache-2.0 Yes Details →
1.1.2.4 31 Mar 2016 H2 M2 Apache-2.0 Yes Details →
1.1.2.3 31 Mar 2016 H2 M2 Apache-2.0 Yes Details →
1.1.2.2 29 Mar 2016 H2 M2 Apache-2.0 Yes Details →
1.1.2.1 22 Jan 2016 H2 M2 Apache-2.0 Yes Details →
1.1.2 22 Sep 2015 H2 M2 Apache-2.0 Yes Details →
1.1.2-RC3 16 Jun 2015 H2 M2 Apache-2.0 Yes Details →
1.1.2-RC2 18 May 2015 H2 M2 Apache-2.0 Yes Details →
1.1.2-RC1 13 May 2015 H2 M2 Apache-2.0 Yes Details →
1.1.2-M1 13 May 2015 H2 M2 Apache-2.0 Yes Details →
1.1.1.7 14 Apr 2015 H2 M2 Apache-2.0 Yes Details →
1.1.1.6 26 Oct 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1.5 24 Oct 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1.4 23 Oct 2014 H2 M2 Apache-2.0 Yes Details →
1.0.5.4 12 Sep 2014 H2 M2 Apache-2.0 Yes Details →
1.0.5.3 17 Aug 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1.3 18 Jul 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1.2 18 Jul 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1.1 14 Jul 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1 13 Jul 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1-M4 04 Jul 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1-M3 26 Jun 2014 H2 M2 Apache-2.0 Yes Details →
1.0.5.2 26 Jun 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1-M2 12 Jun 2014 H2 M2 Apache-2.0 Yes Details →
1.0.5.1 12 Jun 2014 H2 M2 Apache-2.0 Yes Details →
1.1.1-M1 15 Nov 2013 H2 M2 Apache-2.0 Yes Details →
1.1.0.1 07 Nov 2013 H2 M2 Apache-2.0 Yes Details →
1.1.0 17 Oct 2013 H2 M2 Apache-2.0 Yes Details →
1.1.0-M4 20 Aug 2013 H2 M2 Apache-2.0 Yes Details →
1.0.5 17 May 2013 H2 M2 Apache-2.0 Yes Details →
1.1.0-M3 28 Mar 2013 H2 M2 Apache-2.0 Yes Details →
1.1.0-M2 28 Mar 2013 H2 M2 Apache-2.0 Yes Details →
1.1.0-M1 27 Mar 2013 H2 M2 Apache-2.0 Yes Details →
1.0.5-M4 19 Mar 2013 H2 M2 Apache-2.0 Yes Details →
1.0.5-M3 28 Sep 2012 H2 M2 Apache-2.0 Yes Details →
1.0.5-M2 27 Sep 2012 H2 M2 Apache-2.0 Yes Details →
1.0.5-M1 11 Sep 2012 H2 M2 Apache-2.0 Yes Details →
1.0.4.1 05 Oct 2011 H2 M2 Apache-2.0 Yes Details →
1.0.4 22 Sep 2011 H2 M2 — Yes Details →
1.0.3.3 09 Sep 2011 H2 M2 — Yes Details →
1.0.3.2 23 Aug 2011 H2 M2 — Yes Details →
1.0.3.1 02 Aug 2011 H2 M2 — Yes Details →
1.0.3 11 Jul 2011 H2 M2 — Yes Details →
1.0.3-rc4 27 Jun 2011 H2 M2 — Yes Details →
1.0.3-rc3 21 Jun 2011 H2 M2 — Yes Details →
1.0.3-rc2 07 Jun 2011 H2 M2 — Yes Details →
1.0.3-rc1 04 Jun 2011 H2 M2 — Yes Details →
1.0.1-rc4 11 Apr 2011 H2 M2 — Yes Details →
1.0.1-rc3 04 Apr 2011 H2 M2 — Yes Details →
1.0.1-rc2 03 Apr 2011 H2 M2 — Yes Details →
1.0.1-rc1 01 Apr 2011 H2 M2 — Yes Details →

All 87 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.xerial.snappy:snappy-java

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-34455: Vulnerability in org.xerial.snappy:snappy-java - Unchecked Chunk Length Leads to DoS 7.5 high 1.1.10.1 15 Jun 2023
CVE-2023-43642: Denial of Service vulnerability in snappy-java 7.5 high 1.1.10.4 25 Sep 2023
CVE-2023-34454: Integer Overflow vulnerability in snappy-java's compress leads to DoS 5.9 medium 1.1.10.1 15 Jun 2023
CVE-2023-34453: Integer Overflow Vulnerability in snappy-java's shuffle Function Leads to DoS 5.9 medium 1.1.10.1 15 Jun 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.xerial.snappy:snappy-java

Is org.xerial.snappy:snappy-java safe to use?

Vulert records 4 vulnerabilities for org.xerial.snappy:snappy-java in Maven: 0 critical, 2 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.xerial.snappy:snappy-java's Vulert package health score?

Vulert scores org.xerial.snappy:snappy-java 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.xerial.snappy:snappy-java affected?

No. 1.1.10.12, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.xerial.snappy:snappy-java should I use?

1.1.10.12 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.xerial.snappy:snappy-java have?

4 vulnerabilities are recorded for org.xerial.snappy:snappy-java in the Maven ecosystem: 0 critical, 2 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.xerial.snappy:snappy-java vulnerabilities disclosed?

0 vulnerabilities were recorded for org.xerial.snappy:snappy-java in the last 12 months, and the oldest entry in this database dates to 15 Jun 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.xerial.snappy:snappy-java are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.xerial.snappy:snappy-java for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.xerial.snappy:snappy-java version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.