VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.google.inject:guice: vulnerability history, versions and safety

com.google.inject:guice is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

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.inject:guice vulnerabilities

Vulert verdict on com.google.inject:guice 7.0.0 i

Updated on 23 Oct 2026

Good news: 7.0.0, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 7.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 2,272 packages i
  • Stars 12,728 i
  • OpenSSF scorecard 5/10 i
  • Last release 41 months ago 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.inject:guice, 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
7.0.0 12 May 2023 none Apache-2.0 — Details →
6.0.0 12 May 2023 none Apache-2.0 — Details →
6.0.0-rc2 04 May 2023 none Apache-2.0 — Details →
7.0.0-rc1 04 May 2023 none Apache-2.0 — Details →
6.0.0-rc1 27 Apr 2023 none Apache-2.0 — Details →
5.1.0 24 Jan 2022 none Apache-2.0 — Details →
5.0.1 26 Feb 2021 none Apache-2.0 — Details →
5.0.0 25 Feb 2021 none Apache-2.0 — Details →
5.0.0-BETA-1 27 Oct 2020 none Apache-2.0 — Details →
4.2.3 19 Mar 2020 none Apache-2.0 — Details →
4.2.2 29 Oct 2018 none Apache-2.0 — Details →
4.2.1 20 Sep 2018 none Apache-2.0 — Details →
4.2.0 28 Feb 2018 none Apache-2.0 — Details →
4.1.0 17 Jun 2016 none Apache-2.0 — Details →
4.0 28 Apr 2015 none Apache-2.0 — Details →
4.0-beta5 24 Sep 2014 none Apache-2.0 — Details →
4.0-beta4 20 Mar 2014 none Apache-2.0 — Details →
4.0-beta 31 Jul 2013 none Apache-2.0 — Details →
3.0 25 Mar 2011 none Apache-2.0 — Details →
3.0-rc3 07 Mar 2011 none Apache-2.0 — Details →
2.0-no_aop 22 Jan 2011 none Apache-2.0 — Details →
3.0-rc2 10 Jan 2011 none Apache-2.0 — Details →
2.0 01 Aug 2009 none Apache-2.0 — Details →
1.0 26 May 2009 none Apache-2.0 — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for com.google.inject:guice

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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.inject:guice

Is com.google.inject:guice safe to use?

Vulert has no vulnerabilities on record for com.google.inject:guice in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is com.google.inject:guice's Vulert package health score?

Vulert scores com.google.inject:guice 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 com.google.inject:guice affected?

No. 7.0.0, 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.inject:guice should I use?

7.0.0 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.inject:guice have?

0 vulnerabilities are recorded for com.google.inject:guice in the Maven ecosystem: 0 critical, 0 high, 0 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 com.google.inject:guice vulnerabilities disclosed?

0 vulnerabilities were recorded for com.google.inject:guice in the last 12 months. 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.inject:guice 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.inject:guice for upcoming vulnerabilities?

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