Vulnerability Database · Maven · Package report

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

com.google.gwt:gwt is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 12 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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.

Vulert verdict on com.google.gwt:gwt 2.10.0 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 2.10.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 52 months ago i
  • Licence non-standard 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.gwt:gwt, 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
2.10.0 22 Jun 2022 none non-standard — Details →
2.9.0 02 May 2020 none non-standard — Details →
2.9.0-RC1 10 Apr 2020 none non-standard — Details →
2.8.2 18 Oct 2017 none non-standard — Details →
2.8.1 18 Apr 2017 none non-standard — Details →
2.8.0 19 Oct 2016 none non-standard — Details →
2.8.0-rc3 29 Sep 2016 none non-standard — Details →
2.8.0-rc2 12 Aug 2016 none non-standard — Details →
2.8.0-rc1 28 Jul 2016 none non-standard — Details →
2.8.0-beta1 03 Dec 2015 none non-standard — Details →
2.7.0 20 Nov 2014 none non-standard — Details →
2.7.0-rc1 29 Oct 2014 none non-standard — Details →
2.7.0-beta1 18 Oct 2014 none non-standard — Details →
2.6.1 09 May 2014 none non-standard — Details →
2.6.1-rc2 29 Apr 2014 none non-standard — Details →
2.6.1-rc1 29 Apr 2014 none non-standard — Details →
2.6.0 23 Jan 2014 none non-standard — Details →
2.6.0-rc4 09 Jan 2014 none non-standard — Details →
2.6.0-rc3 04 Dec 2013 none non-standard — Details →
2.6.0-rc2 02 Dec 2013 none non-standard — Details →
2.6.0-rc1 07 Nov 2013 none non-standard — Details →
2.5.1 11 Mar 2013 none non-standard — Details →
2.5.1-rc1 05 Feb 2013 M1 non-standard Yes Details →
2.5.0 25 Oct 2012 M1 non-standard Yes Details →
2.5.0-rc2 03 Oct 2012 M1 non-standard Yes Details →
2.5.0-rc1 27 Jun 2012 M1 non-standard Yes Details →
2.4.0 08 Sep 2011 M1 non-standard Yes Details →
2.4.0-rc1 22 Jul 2011 M1 non-standard Yes Details →
2.3.0 03 May 2011 M1 non-standard Yes Details →
2.2.0 12 Feb 2011 M1 non-standard Yes Details →
2.2-rc1 27 Jan 2011 M1 non-standard Yes Details →
2.1.1 17 Dec 2010 M1 non-standard Yes Details →
2.1.1-rc1 10 Dec 2010 M1 non-standard Yes Details →
2.1.0 27 Oct 2010 M1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for com.google.gwt:gwt

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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.gwt:gwt

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

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

Vulert scores com.google.gwt:gwt 65/100, which reads as usable, but worth attention. 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.gwt:gwt affected?

No. 2.10.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.gwt:gwt should I use?

2.10.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.gwt:gwt have?

1 vulnerability is recorded for com.google.gwt:gwt in the Maven ecosystem: 0 critical, 0 high, 1 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.gwt:gwt vulnerabilities disclosed?

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

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