CVE-2025-9467 — Possibility to bypass file upload validation on the server-side
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 following mitigation or upgrade. Releases that have fixed this issue include: Product version Vaadin 7.0.0 - 7.7.47 Vaadin 8.0.0 - 8.28.1 Vaadin 14.0.0 - 14.13.0 Vaadin 23.0.0 - 23.6.1 Vaadin 24.0.0 - 24.7.6 Mitigation Upgrade to 7.7.48 Upgrade to 8.28.2 Upgrade to 14.13.1 Upgrade to 23.6.2 Upgrade to 24.7.7 or newer 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 coordinatesVulnerable versionsFixed versioncom.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:vaadin23.0.0 - 23.6.1 ≥23.6.2 com.vaadin:vaadin24.0.0 - 24.7.6 ≥24.7.7com.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
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Maven Com.vaadin:vaadin-server: fixed in version 7.7.48 — github.com (GitHub Security Advisories)
- Maven Com.vaadin:vaadin-server: fixed in version 8.28.2 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Vaadin Framework, Vaadin Vaadin, Vaadin Vaadin-upload-flow…).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Vaadin | Framework | ≥ 7.0.0 and ≤ 7.7.47≥ 8.0.0 and ≤ 8.28.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Vaadin | Vaadin | ≥ 14.0.0 and ≤ 14.13.0≥ 23.0.0 and ≤ 23.6.1≥ 24.0.0 and ≤ 24.7.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Vaadin | Vaadin-upload-flow | ≥ 2.0.0 and ≤ 14.13.0≥ 23.0.0 and ≤ 23.6.1≥ 24.0.0 and ≤ 24.7.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Maven | Com.vaadin:vaadin-server | ≥ 7.0.0 and ≤ 7.7.47≥ 8.0.0 and ≤ 8.28.1 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.3 | CVSS 4.0 | Medium | — | — | security@vaadin.com via NIST National Vulnerability Database |
| 5.3 | CVSS 4.0 | Medium | — | — | Vaadin via CVE Program (cve.org) e CISA ADP |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:D/RE:L/U:Green (score shown at the top: security@vaadin.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 18, 2026 → Oct 30, 2026 · 13 reading(s) · max 0.39%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · maven/com.vaadin:vaadin-server
- Affected products added · vaadin/vaadin, vaadin/framework, vaadin/vaadin-upload-flow
- SSVC assessment updated
- Record published
- CVSS changed · 5.3
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 18, 2026 – Oct 18, 2026
- 1× Official description updated · Oct 18, 2026 – Oct 18, 2026
References
6 on the record
- github.com/vaadin/framework/security/advisories/GHSA-9gfh-4fwj-w3rj
- nvd.nist.gov/vuln/detail/CVE-2025-9467
- vaadin.com/security/cve-2025-9467
- github.com/vaadin/flow-components/pull/7616
- github.com/advisories/GHSA-9gfh-4fwj-w3rj
- github.com/vaadin/flow-components/commit/bfe9e507cdcc5d90a2312c8f0162f798a29ba63
Elsewhere on this site
Related CVEs (same products)
- Low CVE-2026-110737 Push Endpoint Returns Permissive CORS Headers 3d
- High CVE-2026-110803 Session Lock Leak on an Invalid UI Id Allows Denial of Service in Vaadin Framework 8 9d
- High CVE-2026-107588 Multiple Vulnerabilities in the Highcharts Library Bundled with Vaadin Charts 9d
- Medium CVE-2026-91860 Prototype Pollution in Vaadin Charts and Component Base via Unfiltered Deep Merge Sep 30, 2026
- Medium CVE-2026-93547 Missing Authorization Check in Vaadin Spreadsheet Allows Cell Comments to Be Written to Protected Sheets and Locked Cells Sep 30, 2026
- Medium CVE-2026-2742 Unauthorized session creation via reserved framework path access Mar 10, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-9467 is "Possibility to bypass file upload validation on the server-side", rated Medium. It affects Framework (Vaadin); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.