How severe is CVE-2026-1337?

No CVSS score has been assigned to CVE-2026-1337 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-1337?

CVE-2026-1337 affects the following packages: neo4j (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-1337?

Update neo4j to 2026.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-1337 is resolved across your whole dependency graph.

How do I detect CVE-2026-1337 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neo4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-1337 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-1337 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2026-1337, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2026-1337?

CVE-2026-1337 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-1337?

CVE-2026-1337 is classified as CWE-117 (CWE-117). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-1337 published, and has it been updated?

CVE-2026-1337 was published on February 26, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2026-1337 — neo4j

CVE-2026-1337 is a CWE-117 vulnerability in neo4j. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for neo4j — see the affected versions and patch details below.

Insufficient escaping of unicode characters in query log

Also known asBIT-neo4j-enterprise-2026-1337GHSA-xr72-g735-4vwp

Published

Feb 26, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-1337.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦neo4j

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`neo4j`	all versions	2026.1.0

Affected Products

1 product · 2 configurations

Application

neo4jneo4j

< 2026.01.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

JoakimBulow/CVE-2026-1337

CVE-2026-1337 - Neo4j - Log Injection

⭐ 5🍴 3Jun 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neo4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neo4j to 2026.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-1337 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-1337 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works