CVE-2026-1337: Neo4j Insufficient Unicode Escaping in Query Log Leading to XSS
Summary
CVE-2026-1337: Neo4j Enterprise and Community editions have insufficient escaping of unicode characters in query log. Affects org.neo4j:neo4j versions < 2026.01. Fixed in 2026.01. How to fix ↓
Also tracked for
- neo4j-enterprise · Bitnami
- neo4j · Bitnami
The same CVE-2026-1337 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Neo4j is a popular open-source graph database management system that provides a robust platform for storing and querying graph data. It is available in both Community and Enterprise editions, offering features such as ACID compliance, high availability, and scalability. However, prior to version 2026.01, Neo4j had a vulnerability related to insufficient escaping of unicode characters in its query logs, which could potentially expose users to cross-site scripting (XSS) attacks when logs are viewed in HTML format.
Vulnerability Detail
The vulnerability arises from the inadequate handling of unicode characters in the query logs generated by Neo4j. If a user opens these logs in a tool that interprets them as HTML, it could allow an attacker to inject malicious scripts, leading to XSS. Although there is no direct security impact on Neo4j products, it is crucial for users to treat logs as plain text to mitigate any risks associated with this vulnerability.
How To Fix
Minimum fixed version
2026.01
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a precaution, users of versions prior to 2026.01 should treat the query logs as plain text and avoid opening them in any HTML-rendering tools. This can help prevent potential XSS attacks until the software is updated.
Conclusion
In summary, CVE-2026-1337 highlights a vulnerability in Neo4j related to insufficient escaping of unicode characters in query logs, which can lead to XSS attacks. Users are advised to update to version 2026.01 or later to mitigate this risk and should treat logs as plain text if using earlier versions.
See every vulnerability recorded for org.neo4j:neo4j →
FAQ
The CVE identifier for this vulnerability is CVE-2026-1337.
Neo4j versions prior to 2026.01 are affected by this vulnerability.
The primary risk is the possibility of XSS attacks if query logs are opened in HTML-rendering tools.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
The CVSS score for this vulnerability is 1.1, indicating a low severity level.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.neo4j:neo4j.
