# CVE-2026-1497: Incorrect privilege assignment in composite databases

> Incorrect namespace resolution in Neo4j Enterprise allows admins to inadvertently grant users access to unintended local or remote databases.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** BIT-neo4j-2026-1497, BIT-neo4j-enterprise-2026-1497, GHSA-pr32-4ghw-rwcv, MINI-3ggw-p6vp-2h36, MINI-44vm-vrr5-79wp, MINI-cjwc-45cm-9jpc, MINI-g9qh-5xww-8f8q, MINI-mjp7-2pg7-8cxj, MINI-p4vf-xh4m-fhhx, MINI-pq2r-786x-93x9, MINI-vj9w-rrhf-xgcx, MINI-w7h9-52mf-h5xw, MINI-wh3w-pch3-6wh3

## What is CVE-2026-1497?

CVE-2026-1497 is a low-severity missing authorization vulnerability in neo4j Enterprise Edition, published on 11 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-1497?

2 open source packages ship an affected version, including neo4j-enterprise and neo4j. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `neo4j-enterprise` | Bitnami | All versions | 5.26.22, 2026.2.0 |
| `neo4j` | Bitnami | All versions | 5.26.22, 2026.2.0 |

Products: Neo4j Neo4j.

## How do I fix CVE-2026-1497?

Upgrade neo4j-enterprise to a fixed version for your release line: 5.26.22 or 2026.2.0.

## Is CVE-2026-1497 being exploited?

There is no known exploitation of CVE-2026-1497 in the wild and no public exploit code.

## Other vulnerabilities in neo4j Enterprise Edition

- [CVE-2021-34371](https://insights.sbomify.com/CVE-2021-34371/): Deserialization of Untrusted Data in Neo4j (critical 9.8)
- [CVE-2018-18389](https://insights.sbomify.com/CVE-2018-18389/): Incorrect access control in Neo4j Enterprise Database Server via LDAP authentication (critical 9.8)
- [CVE-2013-7259](https://insights.sbomify.com/CVE-2013-7259/): Neo4J vulnerable to Cross-Site Request Forgery (medium 6.8)
- [CVE-2024-34517](https://insights.sbomify.com/CVE-2024-34517/): Neo4j Cypher component mishandles IMMUTABLE privileges (medium 6.5)
- [CVE-2026-14587](https://insights.sbomify.com/CVE-2026-14587/): Unathenticated connection can hold Bolt channel open (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1497 and fix it if it is affected.

What it is: CVE-2026-1497 is a low-severity missing authorization vulnerability in neo4j Enterprise Edition, published on 11 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-1497 in the wild and no public exploit code.

Affected packages and fixed versions:
- neo4j-enterprise (Bitnami): affected all versions; fixed in 5.26.22, 2026.2.0
- neo4j (Bitnami): affected all versions; fixed in 5.26.22, 2026.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1497/ (Markdown: https://insights.sbomify.com/CVE-2026-1497/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1497
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1497
- OSV: https://osv.dev/vulnerability/CVE-2026-1497

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1497/
Summaries are generated and may contain mistakes; the official description above is the record.