VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.google.guava:guava: vulnerability history, versions and safety

com.google.guava:guava is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 69 releases, from Jun 2020 to Jun 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M2 L1
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 com.google.guava:guava vulnerabilities

Vulert verdict on com.google.guava:guava 33.7.2-jre i

Updated on 23 Oct 2026

Good news: 33.7.2-jre, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 91/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 33.7.2-jre — unaffected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 14 Jun 2023 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Depended on by 3,701 packages i
  • Stars 51,916 i
  • OpenSSF scorecard 6/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 com.google.guava:guava, 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
33.7.2-android 29 Sep 2026 none Apache-2.0 — Details →
33.7.2-jre 29 Sep 2026 none Apache-2.0 — Details →
33.7.1-jre 18 Aug 2026 none Apache-2.0 — Details →
33.7.1-android 18 Aug 2026 none Apache-2.0 — Details →
33.7.0-jre 17 Aug 2026 none Apache-2.0 — Details →
33.7.0-android 17 Aug 2026 none Apache-2.0 — Details →
33.6.0-jre 14 Apr 2026 none Apache-2.0 — Details →
33.6.0-android 14 Apr 2026 none Apache-2.0 — Details →
33.5.0-jre 17 Sep 2025 none Apache-2.0 — Details →
33.5.0-android 17 Sep 2025 none Apache-2.0 — Details →
33.4.8-jre 14 Apr 2025 none Apache-2.0 — Details →
33.4.8-android 14 Apr 2025 none Apache-2.0 — Details →
33.4.7-jre 08 Apr 2025 none Apache-2.0 — Details →
33.4.7-android 08 Apr 2025 none Apache-2.0 — Details →
33.4.6-jre 25 Mar 2025 none Apache-2.0 — Details →
33.4.6-android 25 Mar 2025 none Apache-2.0 — Details →
33.4.5-jre 19 Mar 2025 none Apache-2.0 — Details →
33.4.4-jre 19 Mar 2025 none Apache-2.0 — Details →
33.4.3-jre 19 Mar 2025 none Apache-2.0 — Details →
33.4.1-jre 19 Mar 2025 none Apache-2.0 — Details →
33.4.2-jre 19 Mar 2025 none Apache-2.0 — Details →
33.4.5-android 19 Mar 2025 none Apache-2.0 — Details →
33.4.3-android 19 Mar 2025 none Apache-2.0 — Details →
33.4.4-android 19 Mar 2025 none Apache-2.0 — Details →
33.4.1-android 19 Mar 2025 none Apache-2.0 — Details →
33.4.2-android 19 Mar 2025 none Apache-2.0 — Details →
33.4.0-jre 16 Dec 2024 none Apache-2.0 — Details →
33.4.0-android 16 Dec 2024 none Apache-2.0 — Details →
33.3.1-jre 23 Sep 2024 none Apache-2.0 — Details →
33.3.1-android 23 Sep 2024 none Apache-2.0 — Details →
33.3.0-jre 16 Aug 2024 none Apache-2.0 — Details →
33.3.0-android 16 Aug 2024 none Apache-2.0 — Details →
33.2.1-jre 31 May 2024 none Apache-2.0 — Details →
33.2.1-android 31 May 2024 none Apache-2.0 — Details →
33.2.0-jre 01 May 2024 none Apache-2.0 — Details →
33.2.0-android 01 May 2024 none Apache-2.0 — Details →
33.1.0-jre 13 Mar 2024 none Apache-2.0 — Details →
33.1.0-android 13 Mar 2024 none Apache-2.0 — Details →
33.0.0-jre 18 Dec 2023 none Apache-2.0 — Details →
33.0.0-android 18 Dec 2023 none Apache-2.0 — Details →
32.1.3-jre 10 Oct 2023 none Apache-2.0 — Details →
32.1.3-android 10 Oct 2023 none Apache-2.0 — Details →
32.1.2-jre 31 Jul 2023 none Apache-2.0 — Details →
32.1.2-android 31 Jul 2023 none Apache-2.0 — Details →
32.1.1-jre 30 Jun 2023 none Apache-2.0 — Details →
32.1.1-android 30 Jun 2023 none Apache-2.0 — Details →
32.1.0-jre 29 Jun 2023 none Apache-2.0 — Details →
32.1.0-android 29 Jun 2023 none Apache-2.0 — Details →
32.0.1-jre 08 Jun 2023 none Apache-2.0 — Details →
32.0.1-android 08 Jun 2023 none Apache-2.0 — Details →
32.0.0-jre 26 May 2023 M1 L1 Apache-2.0 Yes Details →
32.0.0-android 26 May 2023 none Apache-2.0 — Details →
31.1-jre 28 Feb 2022 M1 L1 Apache-2.0 Yes Details →
31.1-android 28 Feb 2022 M1 L1 Apache-2.0 Yes Details →
31.0.1-jre 27 Sep 2021 M1 L1 Apache-2.0 Yes Details →
31.0.1-android 27 Sep 2021 M1 L1 Apache-2.0 Yes Details →
31.0-jre 24 Sep 2021 M1 L1 Apache-2.0 Yes Details →
31.0-android 24 Sep 2021 M1 L1 Apache-2.0 Yes Details →
30.1.1-jre 19 Mar 2021 M1 L1 Apache-2.0 Yes Details →
30.1.1-android 19 Mar 2021 M1 L1 Apache-2.0 Yes Details →
30.1-jre 14 Dec 2020 M1 L1 Apache-2.0 Yes Details →
30.1-android 14 Dec 2020 M1 L1 Apache-2.0 Yes Details →
30.0-jre 16 Oct 2020 M1 L1 Apache-2.0 Yes Details →
30.0-android 16 Oct 2020 M1 L1 Apache-2.0 Yes Details →
29.0-jre 13 Apr 2020 M1 L1 Apache-2.0 Yes Details →
29.0-android 13 Apr 2020 M1 L1 Apache-2.0 Yes Details →
28.2-jre 27 Dec 2019 M1 L1 Apache-2.0 Yes Details →
28.2-android 27 Dec 2019 M1 L1 Apache-2.0 Yes Details →
28.1-jre 28 Aug 2019 M1 L1 Apache-2.0 Yes Details →
28.1-android 28 Aug 2019 M1 L1 Apache-2.0 Yes Details →
28.0-jre 11 Jun 2019 M1 L1 Apache-2.0 Yes Details →
28.0-android 11 Jun 2019 M1 L1 Apache-2.0 Yes Details →
27.1-jre 08 Mar 2019 M1 L1 Apache-2.0 Yes Details →
27.1-android 08 Mar 2019 M1 L1 Apache-2.0 Yes Details →
27.0.1-android 19 Nov 2018 M1 L1 Apache-2.0 Yes Details →
27.0.1-jre 19 Nov 2018 M1 L1 Apache-2.0 Yes Details →
27.0-jre 18 Oct 2018 M1 L1 Apache-2.0 Yes Details →
27.0-android 18 Oct 2018 M1 L1 Apache-2.0 Yes Details →
26.0-jre 01 Aug 2018 M1 L1 Apache-2.0 Yes Details →
26.0-android 01 Aug 2018 M1 L1 Apache-2.0 Yes Details →
23.6.1-jre 29 May 2018 M2 L1 Apache-2.0 Yes Details →
23.6.1-android 29 May 2018 M2 L1 Apache-2.0 Yes Details →
25.1-jre 23 May 2018 M1 L1 Apache-2.0 Yes Details →
25.1-android 23 May 2018 M1 L1 Apache-2.0 Yes Details →
24.1.1-jre 26 Apr 2018 M1 L1 Apache-2.0 Yes Details →
24.1.1-android 26 Apr 2018 M1 L1 Apache-2.0 Yes Details →
25.0-jre 25 Apr 2018 M1 L1 Apache-2.0 Yes Details →
25.0-android 25 Apr 2018 M1 L1 Apache-2.0 Yes Details →
24.1-jre 14 Mar 2018 M2 L1 Apache-2.0 Yes Details →
24.1-android 14 Mar 2018 M2 L1 Apache-2.0 Yes Details →
24.0-jre 01 Feb 2018 M2 L1 Apache-2.0 Yes Details →
24.0-android 01 Feb 2018 M2 L1 Apache-2.0 Yes Details →
23.6-jre 21 Dec 2017 M2 L1 Apache-2.0 Yes Details →
23.6-android 21 Dec 2017 M2 L1 Apache-2.0 Yes Details →
23.5-jre 22 Nov 2017 M2 L1 Apache-2.0 Yes Details →
23.5-android 22 Nov 2017 M2 L1 Apache-2.0 Yes Details →
23.4-jre 09 Nov 2017 M2 L1 Apache-2.0 Yes Details →
23.4-android 09 Nov 2017 M2 L1 Apache-2.0 Yes Details →
23.3-jre 26 Oct 2017 M2 L1 Apache-2.0 Yes Details →
23.3-android 26 Oct 2017 M2 L1 Apache-2.0 Yes Details →
23.2-jre 11 Oct 2017 M2 L1 — Yes Details →
23.2-android 11 Oct 2017 M2 L1 — Yes Details →
23.1-jre 27 Sep 2017 M2 L1 — Yes Details →
23.1-android 27 Sep 2017 M2 L1 — Yes Details →
23.0 04 Aug 2017 M2 L1 — Yes Details →
23.0-android 04 Aug 2017 M2 L1 — Yes Details →
23.0-rc1-android 25 Jul 2017 M2 L1 — Yes Details →
23.0-rc1 24 Jul 2017 M2 L1 — Yes Details →
22.0-android 22 May 2017 M2 L1 — Yes Details →
22.0 22 May 2017 M2 L1 — Yes Details →
22.0-rc1 02 May 2017 M2 L1 — Yes Details →
22.0-rc1-android 02 May 2017 M2 L1 — Yes Details →
21.0 12 Jan 2017 M2 L1 — Yes Details →
21.0-rc2 03 Jan 2017 M2 L1 — Yes Details →
21.0-rc1 19 Dec 2016 M2 L1 — Yes Details →
20.0 28 Oct 2016 M2 L1 — Yes Details →
20.0-rc1 06 Oct 2016 M2 L1 — Yes Details →
19.0 09 Dec 2015 M2 L1 — Yes Details →
19.0-rc3 01 Dec 2015 M2 L1 — Yes Details →
19.0-rc2 17 Sep 2015 M2 L1 — Yes Details →

The newest 120 of 160 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for com.google.guava:guava

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2018-10237: Denial of Service in Google Guava 5.9 medium 24.1.1-android 15 Jun 2020
CVE-2023-2976: Insecure Use of Temporary Directory in Google Guava 5.5 medium 32.0.0-android 14 Jun 2023
CVE-2020-8908: Information Disclosure in Guava 3.3 low 32.0.0-android 25 Mar 2021

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 com.google.guava:guava

Is com.google.guava:guava safe to use?

Vulert records 3 vulnerabilities for com.google.guava:guava in Maven: 0 critical, 0 high, 2 medium and 1 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 com.google.guava:guava's Vulert package health score?

Vulert scores com.google.guava:guava 91/100, which reads as healthy. 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 com.google.guava:guava affected?

No. 33.7.2-jre, 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 com.google.guava:guava should I use?

33.7.2-jre 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 com.google.guava:guava have?

3 vulnerabilities are recorded for com.google.guava:guava in the Maven ecosystem: 0 critical, 0 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.google.guava:guava vulnerabilities disclosed?

0 vulnerabilities were recorded for com.google.guava:guava in the last 12 months, and the oldest entry in this database dates to 15 Jun 2020. 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 com.google.guava:guava 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 com.google.guava:guava for upcoming vulnerabilities?

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