How severe is GHSA-fr26-qjc8-mvjx?

GHSA-fr26-qjc8-mvjx 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 GHSA-fr26-qjc8-mvjx?

GHSA-fr26-qjc8-mvjx affects the following packages: com.vaadin:flow-server (Maven), com.vaadin:flow-server (Maven), com.vaadin:flow-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fr26-qjc8-mvjx?

Update com.vaadin:flow-server to 1.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fr26-qjc8-mvjx is resolved across your whole dependency graph.

How do I detect GHSA-fr26-qjc8-mvjx in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:flow-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fr26-qjc8-mvjx 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.

How does O3 Security protect against GHSA-fr26-qjc8-mvjx?

O3 pinpoints whether GHSA-fr26-qjc8-mvjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fr26-qjc8-mvjx actively exploited in the wild?

No public exploit code has been indexed for GHSA-fr26-qjc8-mvjx 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.

When was GHSA-fr26-qjc8-mvjx published, and has it been updated?

GHSA-fr26-qjc8-mvjx was published on October 13, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-fr26-qjc8-mvjx

MEDIUM

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

Published

Oct 13, 2021

Updated

Dec 2, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

☕com.vaadin:flow-server☕com.vaadin:flow-server☕com.vaadin:flow-server

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:flow-server`	≥ 1.0.0&&< 1.0.15	1.0.15
☕Maven	`com.vaadin:flow-server`	≥ 1.1.0&&< 2.6.2	2.6.2
☕Maven	`com.vaadin:flow-server`	≥ 3.0.0&&< 6.0.10	6.0.10

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:flow-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.vaadin:flow-server to 1.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fr26-qjc8-mvjx 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.
How O3 protects you
O3 pinpoints whether GHSA-fr26-qjc8-mvjx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fr26-qjc8-mvjx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

O3 Security · Impact-Aware SCA

Is GHSA-fr26-qjc8-mvjx in your dependencies?

O3 detects GHSA-fr26-qjc8-mvjx across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works