5.4Medium
Neo4j Neo4j
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
What this means for your business
- It affects Neo4j. It matters if your company, or a supplier that handles your data, runs it.
- Code showing how to exploit it has been published, but real attacks have not been confirmed.
- An attacker can use it remotely, over a network, with an ordinary user login, but only after tricking someone into an action such as opening a file or a link.
What to do
- 1Check whether your company or your suppliers run Neo4j, and which version. The affected versions are listed further down this page.
- 2If you do, follow the vendor's guidance. No patch reference has been published yet.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 5.4 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N- CVSS v4
- 1.1
- Weakness
- CWE-117
- Assigned by
- 3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6
Dates
- Published
- 2026-02-06
- Last modified
- 2026-08-28
- Sources
- NVD
Affected products
- Neo4j Neo4j- 2026.01.0
As listed in the NVD configuration data. Not a statement about your estate.