Vulnerability Database · Maven · Package report

com.vaadin:vaadin-bom: vulnerability history, versions and safety

com.vaadin:vaadin-bom is a package in the Maven ecosystem. Vulert records 18 vulnerabilities for it across 0 release, from Apr 2021 to Nov 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded H5 M10 L3
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.vaadin:vaadin-bom 25.3.3 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 25.3.3 — unaffected i
  • Vulnerabilities on record 18 over 1 year · 0 in the last year i
  • Latest disclosure 03 Nov 2021 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Stars 683 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 com.vaadin:vaadin-bom, 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
25.2.12 21 Oct 2026 none Apache-2.0 — Details →
25.3.3 20 Oct 2026 none Apache-2.0 — Details →
24.4.26 19 Oct 2026 none non-standard — Details →
24.7.17 19 Oct 2026 none non-standard — Details →
24.10.12 19 Oct 2026 none Apache-2.0 — Details →
24.9.24 19 Oct 2026 none Apache-2.0 — Details →
14.14.8 19 Oct 2026 none non-standard — Details →
23.6.17 19 Oct 2026 none Apache-2.0 — Details →
7.7.55 14 Oct 2026 none Apache-2.0 — Details →
25.2.11 12 Oct 2026 none Apache-2.0 — Details →
8.32.2 12 Oct 2026 none Apache-2.0 — Details →
25.3.2 12 Oct 2026 none Apache-2.0 — Details →
24.4.25 08 Oct 2026 none Apache-2.0 — Details →
24.4.24 08 Oct 2026 none Apache-2.0 — Details →
24.7.16 08 Oct 2026 none Apache-2.0 — Details →
23.6.16 06 Oct 2026 none Apache-2.0 — Details →
24.10.11 06 Oct 2026 none Apache-2.0 — Details →
24.9.23 06 Oct 2026 none Apache-2.0 — Details →
25.2.10 05 Oct 2026 none Apache-2.0 — Details →
25.3.1 05 Oct 2026 none Apache-2.0 — Details →
14.14.7 28 Sep 2026 none non-standard — Details →
25.2.9 25 Sep 2026 none Apache-2.0 — Details →
25.1.13 24 Sep 2026 none Apache-2.0 — Details →
23.6.15 23 Sep 2026 none Apache-2.0 — Details →
25.3.0 22 Sep 2026 none Apache-2.0 — Details →
24.9.22 21 Sep 2026 none Apache-2.0 — Details →
25.3.0-rc1 16 Sep 2026 none Apache-2.0 — Details →
25.2.8 15 Sep 2026 none Apache-2.0 — Details →
8.32.1 14 Sep 2026 none Apache-2.0 — Details →
25.1.12 14 Sep 2026 none Apache-2.0 — Details →
25.3.0-beta3 14 Sep 2026 none Apache-2.0 — Details →
7.7.54 11 Sep 2026 none Apache-2.0 — Details →
23.6.14 11 Sep 2026 none Apache-2.0 — Details →
24.9.21 10 Sep 2026 none Apache-2.0 — Details →
24.10.10 09 Sep 2026 none Apache-2.0 — Details →
14.14.6 09 Sep 2026 none non-standard — Details →
25.3.0-beta2 09 Sep 2026 none Apache-2.0 — Details →
25.2.7 07 Sep 2026 none Apache-2.0 — Details →
25.3.0-beta1 02 Sep 2026 none Apache-2.0 — Details →
8.32.0 17 Aug 2026 none Apache-2.0 — Details →
14.14.5 11 Aug 2026 none non-standard — Details →
23.6.13 11 Aug 2026 none Apache-2.0 — Details →
24.9.20 11 Aug 2026 none Apache-2.0 — Details →
24.10.9 11 Aug 2026 none Apache-2.0 — Details →
25.1.11 10 Aug 2026 none Apache-2.0 — Details →
25.2.6 10 Aug 2026 none Apache-2.0 — Details →
25.2.5 03 Aug 2026 none Apache-2.0 — Details →
25.2.4 28 Jul 2026 none Apache-2.0 — Details →
25.1.10 28 Jul 2026 none Apache-2.0 — Details →
14.14.4 24 Jul 2026 none non-standard — Details →
24.9.19 17 Jul 2026 none Apache-2.0 — Details →
24.10.8 17 Jul 2026 none Apache-2.0 — Details →
23.6.12 16 Jul 2026 none Apache-2.0 — Details →
25.0.13 16 Jul 2026 none Apache-2.0 — Details →
25.2.3 15 Jul 2026 none Apache-2.0 — Details →
23.6.11 13 Jul 2026 none Apache-2.0 — Details →
25.2.2 10 Jul 2026 none Apache-2.0 — Details →
25.1.9 02 Jul 2026 none Apache-2.0 — Details →
25.2.1 26 Jun 2026 none Apache-2.0 — Details →
25.2.0 23 Jun 2026 none Apache-2.0 — Details →
25.2.0-rc1 17 Jun 2026 none Apache-2.0 — Details →
7.7.53 17 Jun 2026 none Apache-2.0 — Details →
25.2.0-beta3 16 Jun 2026 none Apache-2.0 — Details →
25.1.8 15 Jun 2026 none Apache-2.0 — Details →
25.2.0-beta2 12 Jun 2026 none Apache-2.0 — Details →
24.10.7 10 Jun 2026 none Apache-2.0 — Details →
24.9.18 10 Jun 2026 none Apache-2.0 — Details →
25.0.12 09 Jun 2026 none Apache-2.0 — Details →
25.1.7 09 Jun 2026 none Apache-2.0 — Details →
25.2.0-beta1 27 May 2026 none Apache-2.0 — Details →
25.1.6 25 May 2026 none Apache-2.0 — Details →
24.10.6 21 May 2026 none Apache-2.0 — Details →
23.7.0-beta2 07 May 2026 none Apache-2.0 — Details →
24.9.17 05 May 2026 none Apache-2.0 — Details →
24.10.4 05 May 2026 none Apache-2.0 — Details →
25.0.11 05 May 2026 none Apache-2.0 — Details →
25.1.5 05 May 2026 none Apache-2.0 — Details →
23.6.10 04 May 2026 none Apache-2.0 — Details →
14.14.3 04 May 2026 none non-standard — Details →
25.1.4 29 Apr 2026 none Apache-2.0 — Details →
25.0.10 28 Apr 2026 none Apache-2.0 — Details →
8.31.1 27 Apr 2026 none Apache-2.0 — Details →
24.10.3 27 Apr 2026 none Apache-2.0 — Details →
24.9.16 27 Apr 2026 none Apache-2.0 — Details →
14.14.2 22 Apr 2026 none non-standard — Details →
25.0.9 20 Apr 2026 none Apache-2.0 — Details →
25.1.3 17 Apr 2026 none Apache-2.0 — Details →
25.1.2 16 Apr 2026 none Apache-2.0 — Details →
7.7.52 14 Apr 2026 none Apache-2.0 — Details →
24.10.1 02 Apr 2026 none Apache-2.0 — Details →
8.31.0 02 Apr 2026 none Apache-2.0 — Details →
24.9.14 01 Apr 2026 none Apache-2.0 — Details →
25.1.1 30 Mar 2026 none Apache-2.0 — Details →
25.0.8 26 Mar 2026 none Apache-2.0 — Details →
25.1.0 25 Mar 2026 none Apache-2.0 — Details →
25.1.0-rc2 19 Mar 2026 none Apache-2.0 — Details →
25.1.0-rc1 18 Mar 2026 none Apache-2.0 — Details →
24.10.0 17 Mar 2026 none Apache-2.0 — Details →
24.10.0-beta1 13 Mar 2026 none Apache-2.0 — Details →
25.1.0-beta3 12 Mar 2026 none Apache-2.0 — Details →
23.6.9 11 Mar 2026 none — — Details →
25.0.7 10 Mar 2026 none — — Details →
24.9.13 10 Mar 2026 none — — Details →
25.1.0-beta2 09 Mar 2026 none — — Details →
25.1.0-beta1 02 Mar 2026 none — — Details →
25.0.6 25 Feb 2026 none — — Details →
24.9.12 23 Feb 2026 none — — Details →
23.6.8 18 Feb 2026 none — — Details →
25.0.5 09 Feb 2026 none — — Details →
24.9.11 09 Feb 2026 none — — Details →
7.7.51 06 Feb 2026 none — — Details →
8.30.1 06 Feb 2026 none — — Details →
10.0.26 05 Feb 2026 none — — Details →
14.11.14 05 Feb 2026 none — — Details →
23.4.2 05 Feb 2026 none — — Details →
24.0.15 02 Feb 2026 none — — Details →
24.1.18 01 Feb 2026 none — — Details →
24.3.21 01 Feb 2026 none — — Details →
24.1.17 01 Feb 2026 none — — Details →
24.2.13 30 Jan 2026 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 18

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

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.vaadin:vaadin-bom

Is com.vaadin:vaadin-bom safe to use?

Vulert records 18 vulnerabilities for com.vaadin:vaadin-bom in Maven: 0 critical, 5 high, 10 medium and 3 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.vaadin:vaadin-bom's Vulert package health score?

Vulert scores com.vaadin:vaadin-bom 68/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.vaadin:vaadin-bom affected?

No. 25.3.3, 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.

How many vulnerabilities does com.vaadin:vaadin-bom have?

18 vulnerabilities are recorded for com.vaadin:vaadin-bom in the Maven ecosystem: 0 critical, 5 high, 10 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.vaadin:vaadin-bom vulnerabilities disclosed?

0 vulnerabilities were recorded for com.vaadin:vaadin-bom in the last 12 months, and the oldest entry in this database dates to 19 Apr 2021. 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.vaadin:vaadin-bom 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.vaadin:vaadin-bom for upcoming vulnerabilities?

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