Is com.vaadin:vaadin-server 7.2 vulnerable?

Maven · 8 releases from 7.2.0 to 7.2.7 · latest com.vaadin:vaadin-server is 8.32.3 · checked 18 Nov 2026

Yes: 4 known advisories

Yes. com.vaadin:vaadin-server 7.2.7, the last 7.2 release, is affected by 4 known security advisories (1 high, 3 medium), including CVE-2020-36320, CVE-2025-15022, CVE-2025-9467. Upgrade to 7.7.50 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=com.vaadin:vaadin-server -DdepVersion=7.7.50 -DforceVersion=true

Is your project on an affected com.vaadin:vaadin-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting com.vaadin:vaadin-server 7.2.7

  • MediumCVE-2025-15022GHSA-7wwv-79xw-rvvg5 Jan 2026

    Vaadin vulnerable to Cross-site Scripting

    Affected
    >=7.0.0 <7.7.50 · >=8.0.0 <8.30.0
    Fixed in
    7.7.50, 8.30.0
  • MediumCVE-2025-9467GHSA-9gfh-4fwj-w3rj4 Sept 2025

    Vaadin Framework possible file bypass via upload validation on the server-side

    Affected
    >=7.0.0 <7.7.48 · >=8.0.0 <8.28.2
    Fixed in
    7.7.48, 8.28.2
  • MediumCVE-2021-31403GHSA-75xc-qvxh-27f819 Apr 2021

    Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8

    Affected
    >=7.0.0 <7.7.24 · >=8.0.0 <8.12.3
    Fixed in
    7.7.24, 8.12.3
  • HighCVE-2020-36320GHSA-42j4-733x-5vcf19 Apr 2021

    Regular expression denial of service (ReDoS) in EmailValidator class in Vaadin 7

    Affected
    >=7.0.0.beta1 <7.7.22
    Fixed in
    7.7.22

Every com.vaadin:vaadin-server 7.2.x release

Affected: 7.2.0 to 7.2.7. Latest com.vaadin:vaadin-server: 8.32.3.

VersionKnown advisories
com.vaadin:vaadin-server 7.2.7CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.6CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.5CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.4CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.3CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.2CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.1CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320
com.vaadin:vaadin-server 7.2.0CVE-2025-15022, CVE-2025-9467, CVE-2021-31403, CVE-2020-36320

Which of your client projects are still on com.vaadin:vaadin-server 7.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact com.vaadin:vaadin-server version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other com.vaadin:vaadin-server versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.