com.vaadin:flow-server vulnerabilities
${project.name}
- Registry
- Maven
- Latest
- 25.3.7
- License
- Apache License Version 2.0
13 known advisories
The latest version, 25.3.7, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=com.vaadin:flow-server -DdepVersion=25.3.7 -DforceVersion=trueIs your project on an affected com.vaadin:flow-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for com.vaadin:flow-server
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
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
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
Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19
- Affected
- >=1.0.0 <1.0.15 · >=1.1.0 <2.6.2 · >=3.0.0 <6.0.10
- Fixed in
- 1.0.15, 2.6.2, 6.0.10
Reflected cross-site scripting in development mode handler in Vaadin
- Affected
- >=2.0.0 <2.6.2 · >=3.0.0 <6.0.10
- Fixed in
- 2.6.2, 6.0.10
Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19
- Affected
- >=2.0.9 <2.5.3 · >=3.0.0 <6.0.6
- Fixed in
- 2.5.3, 6.0.6
Unauthorized client-side property update in UIDL request handler in Vaadin 10 and 11
- Affected
- >=1.0.0 <1.0.6
- Fixed in
- 1.0.6
Reflected cross-site scripting in default RouteNotFoundError view in Vaadin 10 and 11-13
- Affected
- >=1.0.0 <1.0.11 · >=1.1.0 <1.4.3
- Fixed in
- 1.0.11, 1.4.3
Potential sensitive data exposure in applications using Vaadin 15
- Affected
- >=3.0.0 <3.0.6
- Fixed in
- 3.0.6
Directory traversal in development mode handler in Vaadin 14 and 15-17
- Affected
- >=3.0.0 <5.0.0 · >=2.0.0 <2.4.2
- Fixed in
- 2.4.2, 5.0.0
Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18
- Affected
- >=1.0.0 <1.0.14 · >=1.1.0 <2.4.7 · >=3.0.0 <5.0.3
- Fixed in
- 1.0.14, 2.4.7, 5.0.3
OSGi applications using Vaadin 12-14 and 19 vulnerable to server classes and resources exposure
- Affected
- >=1.2.0 <2.4.8 · >=6.0.0 <6.0.1
- Fixed in
- 2.4.8, 6.0.1
Timing side channel vulnerability in endpoint request handler in Vaadin 15-19
- Affected
- >=3.0.0 <5.0.4 · >=6.0.0 <6.0.1
- Fixed in
- 5.0.4, 6.0.1
Is your com.vaadin:flow-server version vulnerable?
- com.vaadin:flow-server 25.3No known advisories in 25.3.7
- com.vaadin:flow-server 25.2No known advisories in 25.2.17
- com.vaadin:flow-server 25.1No known advisories in 25.1.19
- com.vaadin:flow-server 25.0No known advisories in 25.0.15
- com.vaadin:flow-server 24.10No known advisories in 24.10.18
- com.vaadin:flow-server 24.9No known advisories in 24.9.32
- com.vaadin:flow-server 24.81 advisory in 24.8.16
- com.vaadin:flow-server 24.71 advisory in 24.7.20
- com.vaadin:flow-server 24.61 advisory in 24.6.14
- com.vaadin:flow-server 24.51 advisory in 24.5.17
- com.vaadin:flow-server 23.6No known advisories in 23.6.17
- com.vaadin:flow-server 23.51 advisory in 23.5.13
- com.vaadin:flow-server 23.41 advisory in 23.4.2
- com.vaadin:flow-server 23.31 advisory in 23.3.31
- com.vaadin:flow-server 23.23 advisories in 23.2.11
- com.vaadin:flow-server 23.13 advisories in 23.1.12
Which of your client projects still run an old com.vaadin:flow-server?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.