How severe is CVE-2021-31412?

CVE-2021-31412 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-31412?

CVE-2021-31412 affects the following packages: com.vaadin:vaadin-bom (Maven), com.vaadin:vaadin-bom (Maven), com.vaadin:vaadin-bom (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-31412?

Update com.vaadin:vaadin-bom to 10.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-31412 is resolved across your whole dependency graph.

How do I detect CVE-2021-31412 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-31412 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-31412 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-31412 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-31412?

CVE-2021-31412 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-31412?

CVE-2021-31412 is classified as CWE-1295 (CWE-1295), Improper Input Validation (CWE-20). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-31412 published, and has it been updated?

CVE-2021-31412 was published on June 24, 2021 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2021-31412 — vaadin-bom

MEDIUMFix: vaadin/flow#11107

CVE-2021-31412 is a medium-severity (CVSS 5.3) CWE-1295 vulnerability in com.vaadin:vaadin-bom. A fix is available for com.vaadin:vaadin-bom — see the affected versions and patch details below.

Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19

Also known asGHSA-qrg9-f472-qwfm

Published

Jun 24, 2021

Updated

Oct 20, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-31412 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕com.vaadin:vaadin-bom☕com.vaadin:vaadin-bom☕com.vaadin:vaadin-bom

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Improper sanitization of path in default RouteNotFoundError view in com.vaadin:flow-server versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for NotFoundException is provided.

https://vaadin.com/security/cve-2021-31412

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:vaadin-bom`	≥ 10.0.0&&< 10.0.19	10.0.19`com.vaadin:vaadin-bom:10.0.19`
☕Maven	`com.vaadin:vaadin-bom`	≥ 11.0.0&&< 14.6.2	14.6.2`com.vaadin:vaadin-bom:14.6.2`
☕Maven	`com.vaadin:vaadin-bom`	≥ 15.0.0&&< 19.0.9	19.0.9`com.vaadin:vaadin-bom:19.0.9`

Affected Products

2 products · 10 configurations

Application

flowvaadin

≥ 6.0.0 && ≤ 6.0.9

range

Application

vaadinvaadin

≥ 19.0.0 && ≤ 19.0.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.vaadin:vaadin-bom to 10.0.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-31412 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Improper sanitization of path in default `RouteNotFoundError` view in `com.vaadin:flow-server` versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for `NotFoundException` is provided. - https://vaadin.com/security/cve-2021-31412

O3 Security · Impact-Aware SCA

Is CVE-2021-31412 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-1295CWE-1295 CWE-20Improper Input Validation

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

flow

5.5/10

Code-Review10/10

Maintained10/10

Branch-Protection4/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jun 24, 2021

Last updated

Oct 20, 2026

Identifiers

CVE-2021-31412

GHSA-qrg9-f472-qwfm

References

Advisoryvaadin.com Advisorynvd.nist.gov Fixgithub.com Webgithub.com

Related vulnerabilities

This CVE is medium severity; 6 of 8 other CVEs affecting vaadin-bom are rated as high or higher (top: high).

CVE-2021-33611GHSA-jfmf-w293-8xr8GHSA-hw7r-qrhp-5pffCVE-2021-33604CVE-2021-31411CVE-2021-31408CVE-2021-31405GHSA-3h5r-928v-mxhh

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2021-31412 — vaadin-bom

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-31412 in your dependencies?