How severe is GHSA-6hgr-2g6q-3rmc?

GHSA-6hgr-2g6q-3rmc has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6hgr-2g6q-3rmc?

GHSA-6hgr-2g6q-3rmc affects the following packages: com.vaadin:flow-client (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6hgr-2g6q-3rmc?

Update com.vaadin:flow-client to 6.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hgr-2g6q-3rmc is resolved across your whole dependency graph.

How do I detect GHSA-6hgr-2g6q-3rmc in my Maven dependencies?

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

How do I mitigate GHSA-6hgr-2g6q-3rmc 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 GHSA-6hgr-2g6q-3rmc actively exploited in the wild?

No public exploit code has been indexed for GHSA-6hgr-2g6q-3rmc 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-6hgr-2g6q-3rmc published, and has it been updated?

GHSA-6hgr-2g6q-3rmc was published on April 22, 2021 and was last updated on November 28, 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

Not in CISA KEV

MEDIUM severity

Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19GHSA-6hgr-2g6q-3rmc

MEDIUMFix: vaadin/flow#10577

GHSA-6hgr-2g6q-3rmc is a medium-severity (CVSS 6.3) vulnerability in com.vaadin:flow-client. A fix is available for com.vaadin:flow-client — see the affected versions and patch details below.

Published

Apr 22, 2021

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.vaadin:flow-client

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

Authentication.logout() helper in com.vaadin:flow-client versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out.

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:flow-client`	≥ 5.0.0&&< 6.0.5	6.0.5`com.vaadin:flow-client:6.0.5`

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-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.vaadin:flow-client to 6.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hgr-2g6q-3rmc 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

`Authentication.logout()` helper in `com.vaadin:flow-client` versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out. - https://vaadin.com/security/cve-2021-31408

O3 Security · Impact-Aware SCA

Is GHSA-6hgr-2g6q-3rmc in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works