com.vaadin:vaadin vulnerabilities
Vaadin Platform
- Registry
- Maven
- Latest
- 25.3.5
- License
- Apache License Version 2.0
6 known advisories
The latest version, 25.3.5, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=com.vaadin:vaadin -DdepVersion=25.3.5 -DforceVersion=trueIs your project on an affected com.vaadin:vaadin?
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:vaadin
Vaadin Vulnerable to Authentication Bypass When Accessing the /VAADIN Endpoint Without a Trailing Slash
- Affected
- >=25.0.0 <25.0.2 · >=24.0.0 <24.9.8 · >=23.0.0 <23.6.7 · <14.14.1
- Fixed in
- 14.14.1, 23.6.7, 24.9.8, 25.0.2
Vaadin vulnerable to Cross-site Scripting
- Affected
- >=23.1.0 <23.6.6 · >=24.0.0 <24.8.14 · >=24.9.0 <24.9.7
- Fixed in
- 23.6.6, 24.8.14, 24.9.7
Vaadin Platform possible file bypass via upload validation on the server-side
- Affected
- >=14.0.0 <14.13.1 · >=23.0.0 <23.6.2 · >=24.0.0 <24.7.7
- Fixed in
- 14.13.1, 23.6.2, 24.7.7
Vaadin vulnerable to possible information disclosure in non visible components.
- Affected
- >=10.0.0 <10.0.23 · >=11.0.0 <14.10.1 · >=23.0.0 <23.3.13 · >=24.0.0 <24.0.6 · >=24.1.0.alpha1 <24.1.0
- Fixed in
- 10.0.23, 14.10.1, 23.3.13, 24.0.6, 24.1.0
Vaadin vulnerable to possible information disclosure of class and method names in RPC response
- Affected
- >=10.0.0 <10.0.24 · >=11.0.0 <14.10.2 · >=15.0.0 <22.1.0 · >=23.0.0 <23.3.14 · >=24.0.0 <24.0.7 · >=24.1.0.alpha1 <24.1.0
- Fixed in
- 10.0.24, 14.10.2, 22.1.0, 23.3.14, 24.0.7, 24.1.0
Possible information disclosure inside TreeGrid component with default data provider
- Affected
- >=14.8.5 <14.8.10 · >=22.0.6 <22.0.15 · >=23.0.0 <23.0.9
- Fixed in
- 14.8.10, 22.0.15, 23.0.9
Is your com.vaadin:vaadin version vulnerable?
- com.vaadin:vaadin 25.3No known advisories in 25.3.5
- com.vaadin:vaadin 25.2No known advisories in 25.2.14
- com.vaadin:vaadin 25.1No known advisories in 25.1.13
- com.vaadin:vaadin 25.0No known advisories in 25.0.13
- com.vaadin:vaadin 24.10No known advisories in 24.10.14
- com.vaadin:vaadin 24.9No known advisories in 24.9.26
- com.vaadin:vaadin 24.81 advisory in 24.8.17
- com.vaadin:vaadin 24.72 advisories in 24.7.19
- com.vaadin:vaadin 24.63 advisories in 24.6.13
- com.vaadin:vaadin 24.53 advisories in 24.5.15
- com.vaadin:vaadin 23.6No known advisories in 23.6.19
- com.vaadin:vaadin 23.53 advisories in 23.5.18
- com.vaadin:vaadin 23.43 advisories in 23.4.2
- com.vaadin:vaadin 23.33 advisories in 23.3.35
- com.vaadin:vaadin 23.25 advisories in 23.2.17
- com.vaadin:vaadin 23.15 advisories in 23.1.17
Which of your client projects still run an old com.vaadin:vaadin?
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.