dbcve.org
Neo4jApplication

CVE-2026-1471

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 5.26.22 / 2026.01.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Neo4j Enterprise edition versions prior to 2026.01.4 excessively cache authentication context, causing authenticated users to inherit the security context of the first user who authenticated after a server restart. This vulnerability is triggered only in certain non-default SSO configurations that utilize the UserInfo endpoint.

MitigationUpgrade Neo4j Enterprise to version 2026.01.4 or 5.26.22 to resolve the authentication context caching issue. Organizations using SSO with UserInfo endpoint should prioritize this upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Neo4jApplication
Affected:< 5.26.22>= 2025.01.0, < 2026.01.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Neo4j version
    Run `neo4j --version` or check the version from the Neo4j browser via `:server version`, or inspect the file $NEO4J_HOME/lib/neo4j-common.jar for the version manifest
    Affected if Version is below 5.26.22, OR between 2025.01.0 and 2026.01.4 (exclusive)
  2. Confirm Neo4j edition is Enterprise
    Check the license information via `neo4j-admin db info` or inspect the $NEO4J_HOME/conf/neo4j.conf for licensing configuration, or run `CALL dbms.components()` in cypher
    Affected if Edition shown is not Enterprise (vulnerability only affects Enterprise)
  3. Verify SSO authentication is configured
    Inspect $NEO4J_HOME/conf/neo4j.conf for SSO-related settings such as `dbms.security.auth` providers, `dbms.security.sso` settings, or OAuth2/OIDC configuration entries
    Affected if SSO is not configured (vulnerability only triggers with SSO)
  4. Check if UserInfo endpoint is in use
    Review SSO/OIDC provider configuration in neo4j.conf for presence of `user_info_uri`, `userInfoEndpoint`, or similar UserInfo-related settings pointing to an external Identity Provider endpoint
    Affected if UserInfo endpoint is configured in SSO settings

User is affected if Neo4j Enterprise version is in the vulnerable range AND SSO with UserInfo endpoint is configured, as this is the specific non-default configuration that triggers the caching flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.26.22 / 2026.01.4 or later
Fixed in 5.26.222026.01.4
Interim mitigation

Upgrade Neo4j Enterprise to version 2026.01.4 or 5.26.22 to resolve the authentication context caching issue. Organizations using SSO with UserInfo endpoint should prioritize this upgrade.

Recommended fix High confidence

2026.01.4 or 5.26.22

  1. 1. Back up your Neo4j database and configuration files before upgrading
  2. 2. Determine your current Neo4j version by running `neo4j --version` or checking the Neo4j desktop application
  3. 3. Download Neo4j version 2026.01.4 (or 5.26.22) from the official Neo4j download center (neo4j.com/download)
  4. 4. Stop the Neo4j service using `neo4j stop` or your system's service manager
  5. 5. Install the new version following the standard Neo4j installation process for your platform
  6. 6. Ensure your configuration files (neo4j.conf) are compatible with the new version, particularly any SSO-related settings
  7. 7. Start the Neo4j service using `neo4j start` or your system's service manager
  8. 8. Verify the upgrade was successful by checking the version with `neo4j --version` and confirming SSO authentication works correctly
Caveat Review Neo4j release notes for version 2026.01.4 and 5.26.22 for any breaking changes; minor version upgrades typically have minimal compatibility issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Neo4j Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1471 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1471 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data