CVE-2026-1337: Insufficient escaping of unicode characters in query log
Insufficient escaping of unicode characters in query log in Neo4j Enterprise and Community editions prior to 2026.01 can lead to XSS if the user opens the logs in a tool that treats them as HTML. There is no security impact on Neo4j products, but this advisory is released as a precaution to treat the logs as plain text if using versions prior to 2026.01.
Proof of concept exploit: https://github.com/JoakimBulow/CVE-2026-1337
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-1337?
CVE-2026-1337 is classified as having no security impact on Neo4j products.
How do I fix CVE-2026-1337?
To mitigate CVE-2026-1337, upgrade to Neo4j Enterprise or Community editions version 2026.01 or later.
What products are affected by CVE-2026-1337?
CVE-2026-1337 affects Neo4j Enterprise and Community editions prior to version 2026.01.
What type of vulnerability is CVE-2026-1337?
CVE-2026-1337 is a vulnerability related to insufficient escaping of unicode characters in the query log.
What could happen if CVE-2026-1337 is exploited?
If exploited, CVE-2026-1337 could lead to cross-site scripting (XSS) if logs are opened in an HTML-treating tool.