How severe is CVE-2026-1337?

CVE-2026-1337 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2026-1337 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-1337?

CVE-2026-1337 primarily affects Neo4j. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-1337?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-1337 have an EU (EUVD) identifier?

Yes. CVE-2026-1337 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-5683.

When was CVE-2026-1337 published?

CVE-2026-1337 was published on 2026-02-06 and last updated on 2026-06-17.

CVE-2026-1337

CVE-2026-1337 is a medium-severity vulnerability in Neo4j with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-117.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
CVSS v4: 1.1
EPSS exploit prediction: 0% (11th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-5683
Weakness: CWE-117
Affected product: Neo4j
Published: 2026-02-06
Last modified: 2026-06-17

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

Frequently asked questions

What is 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
How severe is CVE-2026-1337?: CVE-2026-1337 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2026-1337 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-1337?: CVE-2026-1337 primarily affects Neo4j. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-1337?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-1337 have an EU (EUVD) identifier?: Yes. CVE-2026-1337 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-5683.
When was CVE-2026-1337 published?: CVE-2026-1337 was published on 2026-02-06 and last updated on 2026-06-17.

References

https://github.com/JoakimBulow/CVE-2026-1337

Affected products (2)

cpe:2.3:a:neo4j:neo4j:*:*:*:*:community:*:*:*
cpe:2.3:a:neo4j:neo4j:*:*:*:*:enterprise:*:*:*

More vulnerabilities in Neo4j

CVE-2026-1524 — Critical (CVSS 9.8): An edgecase in SSO implementation in Neo4j Enterprise edition versions prior to version 2026.02 can lead to…
CVE-2021-34371 — Critical (CVSS 9.8): Neo4j through 3.4.18 (with the shell server enabled) exposes an RMI service that arbitrarily deserializes Java objects,…
CVE-2018-18389 — Critical (CVSS 9.8): Due to incorrect access control in Neo4j Enterprise Database Server 3.4.x before 3.4.9, the setting of LDAP for…
CVE-2026-1497 — High (CVSS 7.2): Incorrect resolving of namespaces in composite databases in Neo4j Enterprise edition prior to versions 2026.02 and…
CVE-2013-7259 — Medium (CVSS 6.8): Multiple cross-site request forgery (CSRF) vulnerabilities in Neo4J 1.9.2 allow remote attackers to hijack the…
CVE-2026-1471 — Medium (CVSS 6.5): Excessive caching of authentication context in Neo4j Enterprise edition versions prior to 2026.01.4 leads to…

All CVEs affecting Neo4j →

Other CWE-117 (Improper Output Neutralization for Logs) vulnerabilities

CVE-2023-46322 — Critical (CVSS 9.8): iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize ssh hostnames in URLs. The hostname's initial…
CVE-2023-46321 — Critical (CVSS 9.8): iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. They may have shell…
CVE-2024-0095 — Critical (CVSS 9.0): NVIDIA Triton Inference Server for Linux and Windows contains a vulnerability where a user can inject forged logs and…
CVE-2024-25047 — High (CVSS 8.6): IBM Cognos Analytics 11.2.0 through 11.2.4 and 12.0.0 through 12.0.2 is vulnerable to injection attacks in application…
CVE-2025-57564 — High (CVSS 8.2): CubeAPM nightly-2025-08-01-1 allow unauthenticated attackers to inject arbitrary log entries into production systems…
CVE-2026-10745 — High (CVSS 7.9): Improper output neutralization for logs vulnerability in upKeeper Solutions upKeeper Instant Privilege Access on…

Browse all CWE-117 (Improper Output Neutralization for Logs) vulnerabilities →