Untargeted information leak via uninitialized Bolt BitMask
Published Oct 31, 2025 · Updated Oct 31, 2025
Neo4j Community and Enterprise editions 5.26.0 through 5.26.14 and 2025.1.0 through 2025.10.0 allow remote attackers to read one byte. The Bolt handshake allocates a self-allocated BitMask without initializing its storage, so a server response can contain a byte retained from a previous connection. No authentication or user interaction is required, but attack requirements are present and the attacker cannot select the leaked value.
Summary
What happened
Neo4j Community and Enterprise editions 5.26.0 through 5.26.14 and 2025.1.0 through 2025.10.0 allow remote attackers to read one byte. The Bolt handshake allocates a self-allocated BitMask without initializing its storage, so a server response can contain a byte retained from a previous connection. No authentication or user interaction is required, but attack requirements are present and the attacker cannot select the leaked value.
The record
- CVE
- CVE-2025-11602
- Published
- Oct 31, 2025
- Updated
- Oct 31, 2025
- Vendor
- Neo4j
- Product
- Neo4j Enterprise Edition
- Classifications
- CWE-226, CAPEC-410
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2025CVE publishedPublication date reported by the CVE source.
- Oct 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2025.1.0 <2025.10.1
- Affected versionversion=5.26.0 <5.26.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo