# Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19

Advisory record · `GHSA-6hgr-2g6q-3rmc`

- **Identifiers:** `GHSA-6hgr-2g6q-3rmc`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 22 Apr 2021
- **Updated:** 28 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Apr 2021, 16:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.vaadin:flow-client` (Maven): affected `>=5.0.0, <6.0.5`; fixed in `6.0.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Vaadin's flow-client package (Maven com.vaadin:flow-client) is affected in versions 5.0.0 up to 6.0.5, with a fix in 6.0.5. The Authentication.logout() helper uses the wrong HTTP method, so when Spring Security CSRF protection is in use, the server session is not invalidated after a user attempts to log out, and a local attacker can still reach Fusion endpoints. Upgrade to flow-client 6.0.5 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.3 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6hgr-2g6q-3rmc)

## Sources

- [GitHub Advisory Database: GHSA-6hgr-2g6q-3rmc](https://github.com/advisories/GHSA-6hgr-2g6q-3rmc)
- [OSV: GHSA-6hgr-2g6q-3rmc](https://osv.dev/vulnerability/GHSA-6hgr-2g6q-3rmc)
- <https://github.com/vaadin/flow/security/advisories/GHSA-6hgr-2g6q-3rmc>
- <https://github.com/vaadin/flow/pull/10577>
- <https://github.com/vaadin/flow/commit/815b967fc84fefa8d3a4d72b9a036f48b0d96326>
- <https://github.com/vaadin/flow>
- <https://vaadin.com/security/cve-2021-31408>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6hgr-2g6q-3rmc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6hgr-2g6q-3rmc/>. Everything for agents: <https://agentprime.io/llms.txt>.
