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

published 2025-09-04 last yr. modified 2025-09-04 last yr.

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### 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. Users of affected versions should apply the upgrade to a more recent Vaadin version.

Patch / fix

fixed in 1 links 2

maven com.vaadin:vaadin-upload-flow 14.13.1, 23.6.2, 24.7.7

github.com/vaadin/flow-components@bfe9e50 commit
github.com/vaadin/flow-components#7616 pull request

Is GHSA-94g8-xv23-7656 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
maven	com.vaadin:vaadin-upload-flow	>=2.0.0, <14.13.1 >=23.0.0, <23.6.2 >=24.0.0, <24.7.7	14.13.1 23.6.2 24.7.7

Classification

Weakness

CWE-20 Improper Input Validation
CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

GitHub Advisory GHSA-94g8-xv23-7656

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.