Advisory record · GHSA-xr72-g735-4vwp

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

CVSS 1.1 LowEPSS 0.0024 · 15th percentile

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.

PackageEcosystemAffectedFixed in
org.neo4j:neo4jMaven<2026.012026.01
Identifiers
GHSA-xr72-g735-4vwp · BIT-neo4j-2026-1337 · BIT-neo4j-enterprise-2026-1337 · CVE-2026-1337
Weakness (CWE)
CWE-117
Published
6 Feb 2026
Updated
10 Sept 2026

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

ScoreRatingCVSSVectorSource
1.1 Low 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 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

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

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.