Vulnerability in Neo4j Community Edition

CVE-2026-1337

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

Published · last modified .

CVSS v3 metric

CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.

EPSS exploit prediction

EPSS: 0.002 (12.1th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 12th percentile — 12.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-1337: held from 0.002 to 0.002.

EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: +0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2026-1337?
CVE-2026-1337 is a medium-severity vulnerability in Neo4j Community Edition, classified under Improper Output Neutralization for Logs. CVSS score: 5.4/10. Published 2026-02-06.
How severe is CVE-2026-1337?
Medium severity. CVSS v3 base score is 5.4 out of 10.
Is CVE-2026-1337 known to be exploited?
2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.