Skip to content
Connect AISign inSign up free
CVE-2026-13371.1LowCWE-117

CVE-2026-1337: Insufficient escaping of unicode characters in query log

neo4j · Enterprise Edition

Vendor fix available · Affected: neo4j Enterprise Edition · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.3%probability of exploitation in the next 30 days
15th percentile
050100

Higher than 15% of scored CVEs

1.1LowCVSS 4.0
Low

DescriptionCVE.org

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 products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • neo4j · Enterprise Editionbefore 2026.01.0
  • neo4j · Community Editionbefore 2026.01.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
neo4j
Published
February 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-1337 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References