All vulnerability reports

Possibility to bypass file upload validation on the server-side

CVE entry
CVE-2025-9467

Overview

When the Vaadin Upload's start listener is used to validate metadata about an incoming upload, it is possible to bypass the upload validation.

See CWE-20 Improper Input Validation

Description

When the Vaadin Upload's start listener is used to validate metadata about an incoming upload, it is possible to bypass the upload validation.

Affected products and mitigation

Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include:

Product version Mitigation
Vaadin 7.0.0 - 7.7.47 Upgrade to 7.7.48 (Vaadin extended maintenance)
Vaadin 8.0.0 - 8.28.1 Upgrade to 8.28.2 (Vaadin extended maintenance)
Vaadin 14.0.0 - 14.13.0 Upgrade to 14.13.1 (Vaadin extended maintenance)
Vaadin 23.0.0 - 23.6.1 Upgrade to 23.6.2 (Vaadin extended maintenance)
Vaadin 24.0.0 - 24.7.6 Upgrade to 24.7.7 or newer (Vaadin extended maintenance)
Vaadin Upload Flow 2.0.0 - 14.13.0 Upgrade to 14.13.1 (Vaadin extended maintenance)
Vaadin Upload Flow 23.0.0 - 23.6.1 Upgrade to 23.6.2 (Vaadin extended maintenance)
Vaadin Upload Flow 24.0.0 - 24.7.6 Upgrade to 24.7.7 or newer (Vaadin extended maintenance)

Please note that Vaadin versions 10-13 and 15-22 are no longer supported and you should update either to the latest 14, 23, 24 version.

Artifacts

Maven coordinates Vulnerable version Fixed version
com.vaadin:vaadin-server  7.0.0 - 7.7.47 ≥7.7.48
com.vaadin:vaadin-server  8.0.0 - 8.28.1 ≥8.28.2
com.vaadin:vaadin  14.0.0 - 14.13.0 ≥14.13.1
com.vaadin:vaadin 23.0.0 - 23.6.1 ≥23.6.2
com.vaadin:vaadin 24.0.0 - 24.7.6 ≥24.7.7
com.vaadin:vaadin-upload-flow 2.0.0 - 14.13.0 ≥14.13.1
com.vaadin:vaadin-upload-flow 23.0.0 - 23.6.1 ≥23.6.2
com.vaadin:vaadin-upload-flow 24.0.0 - 24.7.6 ≥24.7.7

References

  • https://github.com/vaadin/flow-components/pull/7616

History

  • 2026-10-27: the releases that are only available under Vaadin extended maintenance are now marked in the mitigation table
  • 2025-09-03: Initial vulnerability report published