Answer in brief
CVE-2026-1337 records a Unknown severity vulnerability in Neo4j Enterprise and Community editions have insufficient escaping of unicode characters in query log. The current sources do not mark it as known exploited. The current feed maps org.neo4j:neo4j (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.neo4j:neo4j (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| org.neo4j:neo4jmaven | >=0 <2026.01 | 2026.01 |
Published upstream
Feb 6, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Aug 27, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Aug 30, 2026
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
Quoted source text, attributed separately from HOL analysis.