# Neo4j Enterprise and Community editions have insufficient escaping of unicode characters in query log

Advisory record · `GHSA-xr72-g735-4vwp`

- **Identifiers:** `GHSA-xr72-g735-4vwp` · `BIT-neo4j-2026-1337` · `BIT-neo4j-enterprise-2026-1337` · `CVE-2026-1337`
- **State:** Confirmed
- **Severity:** CVSS 1.1 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-117](https://cwe.mitre.org/data/definitions/117.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md)
- **Published:** 6 Feb 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Feb 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.neo4j:neo4j` (Maven): affected `<2026.01`; fixed in `2026.01`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Neo4j Enterprise and Community editions, the org.neo4j:neo4j Maven package, are affected before 2026.01 because query log output does not sufficiently escape Unicode characters. An attacker could cause XSS if a user opens the logs in a tool that renders them as HTML, though the source states there is no direct security impact on Neo4j itself. Upgrade to 2026.01 or later; until then, treat the query logs as plain text.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 1.1 Low, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P`, from CNA (Neo4j)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0024, the 15th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xr72-g735-4vwp)

## Sources

- [GitHub Advisory Database: GHSA-xr72-g735-4vwp](https://github.com/advisories/GHSA-xr72-g735-4vwp)
- [OSV: GHSA-xr72-g735-4vwp](https://osv.dev/vulnerability/GHSA-xr72-g735-4vwp)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-1337>
- <https://github.com/JoakimBulow/CVE-2026-1337>
- <https://github.com/neo4j/neo4j>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xr72-g735-4vwp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xr72-g735-4vwp/>. Everything for agents: <https://agentprime.io/llms.txt>.