Neo4j Community Edition
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Neo4j Community Edition.
By the Year
In 2026 there have been 1 vulnerability in Neo4j Community Edition. Last year, in 2025 Community Edition had 1 security vulnerability published. If vulnerabilities keep coming in at the current rate, it appears that number of security vulnerabilities in Community Edition in 2026 could surpass last years number.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 1 | 0.00 |
| 2025 | 1 | 0.00 |
It may take a day or so for new Community Edition vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Neo4j Community Edition Security Vulnerabilities
Info Disclosure in Neo4j 2026 Pre-2026.01.3 via Log Obfuscation
CVE-2026-1622
- February 04, 2026
Neo4j Enterprise and Community editions versions prior to 2026.01.3 and 5.26.21 are vulnerable to a potential information disclosure by a user who has ability to access the local log files. The "obfuscate_literals" option in the query logs does not redact error information, exposing unredacted data in the query log when a customer writes a query that fails. It can allow a user with legitimate access to the local log files to obtain information they are not authorised to see. If this user is also in a position to run queries and trigger errors, this vulnerability can potentially help them to infer information they are not authorised to see through their intended database access. We recommend upgrading to versions 2026.01.3 (or 5.26.21) where the issue is fixed, and reviewing query log files permissions to ensure restricted access. If your configuration had db.logs.query.obfuscate_literals enabled, and you wish the obfuscation to cover the error messages as well, you need to enable the new configuration setting db.logs.query.obfuscate_errors once you have upgraded Neo4j.
Insertion of Sensitive Information into Log File
Neo4j Bolt Handshake Leakage: One Byte Disclosure
CVE-2025-11602
- October 31, 2025
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.
Sensitive Information in Resource Not Removed Before Reuse
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Neo4j Community Edition or by Neo4j? Click the Watch button to subscribe.
