How severe is CVE-2026-1497?

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

Is CVE-2026-1497 being actively exploited?

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

What products are affected by CVE-2026-1497?

CVE-2026-1497 affects Neo4j. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-1497?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

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

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

When was CVE-2026-1497 published?

CVE-2026-1497 was published on 2026-03-11 and last updated on 2026-06-17.

CVE-2026-1497

CVE-2026-1497 is a high-severity vulnerability in Neo4j with a CVSS 3.x base score of 7.2. 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-863.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v4: 2.0
EPSS exploit prediction: 0% (15th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-11184
Weakness: CWE-863
Affected product: Neo4j
Published: 2026-03-11
Last modified: 2026-06-17

Description

Incorrect resolving of namespaces in composite databases in Neo4j Enterprise edition prior to versions 2026.02 and 5.26.22 can lead to the following scenario: an admin that intends to give a user an access to a remote database constituent "namespace.name" will inadvertently grant access to any local database or remote alias called "name". If such database or alias doesn't exist when the command is run, the privileges will apply if it's created in the future.

Frequently asked questions

What is CVE-2026-1497?: Incorrect resolving of namespaces in composite databases in Neo4j Enterprise edition prior to versions 2026.02 and 5.26.22 can lead to the following scenario: an admin that intends to give a user an access to a remote database constituent "namespace.name" will inadvertently grant access to any local database or remote alias called "name". If such database or alias doesn't exist when the command is run, the privileges will apply if it's created in the future.
How severe is CVE-2026-1497?: CVE-2026-1497 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-1497 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-1497?: CVE-2026-1497 affects Neo4j. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-1497?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-1497 have an EU (EUVD) identifier?: Yes. CVE-2026-1497 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11184.
When was CVE-2026-1497 published?: CVE-2026-1497 was published on 2026-03-11 and last updated on 2026-06-17.

References

https://neo4j.com/security/CVE-2026-1497

Affected products (1)

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-14587 — High (CVSS 7.5): Neo4j's Bolt modern handshake decoder treats an overlong capability bit mask the same way it treats a truncated bit…
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-863 (Incorrect Authorization) vulnerabilities

CVE-2026-69555 — Critical (CVSS 10.0): Incorrect authorization in Azure Arc allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-71398 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary…
CVE-2026-27302 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary…
CVE-2026-48449 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Incorrect Authorization vulnerability that could result in arbitrary…
CVE-2026-48286 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) versions 7.4.3 build 9396 and earlier are affected by an Incorrect Authorization…
CVE-2026-48303 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) versions 7.4.3 build 9394 and earlier are affected by an Incorrect Authorization…

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →