Is com.vaadin:flow-server 23.1 vulnerable?

Maven · 13 releases from 23.1.0 to 23.1.12 · latest com.vaadin:flow-server is 25.3.7 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. com.vaadin:flow-server 23.1.12, the last 23.1 release, is affected by 3 known security advisories (2 medium, 1 low), including CVE-2026-2742, CVE-2023-25499, CVE-2023-25500. Upgrade to 23.6.7 or later to fix all of them.

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

Is your project on an affected com.vaadin:flow-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:flow-server 23.1.12

  • MediumCVE-2026-2742GHSA-rjgh-wgc7-m37j10 Mar 2026

    Vaadin Vulnerable to Authentication Bypass When Accessing the /VAADIN Endpoint Without a Trailing Slash

    Affected
    <14.14.1 · >=23.0.0 <23.6.7 · >=24.0.0 <24.9.8 · >=25.0.0 <25.0.2
    Fixed in
    14.14.1, 23.6.7, 24.9.8, 25.0.2
  • MediumCVE-2023-25499GHSA-5f9v-mv5g-jh5q22 Jun 2023

    Vaadin vulnerable to possible information disclosure in non visible components.

    Affected
    >=1.0.0 <1.0.20 · >=1.1.0 <2.8.10 · >=3.0.0 <9.1.1 · >=23.0.0 <23.3.11 · >=24.0.0 <24.0.8 · >=24.1.0.alpha1 <24.1.0
    Fixed in
    1.0.20, 2.8.10, 9.1.1, 23.3.11, 24.0.8, 24.1.0
  • LowCVE-2023-25500GHSA-ch48-9r3q-pv7x22 Jun 2023

    Vaadin vulnerable to possible information disclosure of class and method names in RPC response

    Affected
    >=1.0.0 <1.0.21 · >=1.1.0 <2.9.3 · >=3.0.0 <9.1.2 · >=23.0.0 <23.3.13 · >=24.0.0 <24.0.9 · >=24.1.alpha1 <24.1.0
    Fixed in
    1.0.21, 2.9.3, 9.1.2, 23.3.13, 24.0.9, 24.1.0

Every com.vaadin:flow-server 23.1.x release

Affected: 23.1.0 to 23.1.12. Latest com.vaadin:flow-server: 25.3.7.

VersionKnown advisories
com.vaadin:flow-server 23.1.12CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.11CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.10CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.9CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.8CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.7CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.6CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.5CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.4CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.3CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.2CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.1CVE-2026-2742, CVE-2023-25499, CVE-2023-25500
com.vaadin:flow-server 23.1.0CVE-2026-2742, CVE-2023-25499, CVE-2023-25500

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

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

Other com.vaadin:flow-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.