dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-58473

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 6 weeks old

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
Cognee before 1.2.0 contains an improper access control vulnerability that allows unauthenticated attackers to overwrite the global LLM provider configuration by self-registering an account and calling the settings endpoint, which performs no admin or superuser check. Attackers can redirect all LLM operations instance-wide to an attacker-controlled endpoint by exploiting the process-wide singleton configuration cache, enabling exfiltration of prompts, uploaded documents, extracted entities, and knowledge graph content from all users.

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 · high confidence

Cognee before 1.2.0 allows unauthenticated users to self-register and call a settings endpoint lacking admin/superuser authorization checks, enabling them to overwrite the global LLM provider configuration through the process-wide singleton cache. This redirects all LLM operations to an attacker-controlled endpoint, exfiltrating prompts, documents, entities, and knowledge graph content from all users.

MitigationUpgrade to Cognee 1.2.0 or later which includes proper authorization checks on the settings endpoint; additionally implement role-based access control to prevent non-admin users from modifying global configuration.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Cognee version
    Check the installed version of Cognee by examining the package.json, setup.py, or by running a version command if available (e.g., pip show cognee, npm list cognee, or checking the deployed application version endpoint)
    Affected if The installed version is before 1.2.0 (versions 1.0.x, 1.1.x, or any version lower than 1.2.0)
  2. Verify self-registration is disabled
    Inspect the authentication configuration or user registration settings to determine if unauthenticated self-registration is allowed. Look for configuration flags like REGISTRATION_OPEN, ALLOW_SIGNUP, or similar in the application configuration files or environment variables
    Affected if Self-registration is enabled and unauthenticated users can create their own accounts
  3. Confirm settings endpoint authorization
    Attempt to access the settings or configuration endpoint (typically /settings, /admin/settings, or /config) with a newly registered non-admin user account and observe whether the request is denied or returns 403 Forbidden
    Affected if The settings endpoint responds successfully to non-admin or unauthenticated requests without returning an authorization error
  4. Inspect LLM provider configuration
    Examine the global LLM provider configuration through the settings endpoint or by inspecting configuration files. Look for fields specifying the LLM endpoint URL, API base, or provider type to see if they point to an unexpected or external endpoint
    Affected if The LLM provider configuration shows an endpoint URL that is not the expected internal or known provider endpoint, or was recently modified

A user is affected if they are running Cognee version below 1.2.0 with self-registration enabled and the settings endpoint accessible without admin authentication, particularly if the LLM provider configuration shows unexpected values.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Cognee 1.2.0 or later which includes proper authorization checks on the settings endpoint; additionally implement role-based access control to prevent non-admin users from modifying global configuration.

Recommended fix Moderate confidence

1.2.0 or later

  1. Upgrade Cognee to version 1.2.0 or later, as this version includes the patch that adds proper authentication and authorization checks to the settings endpoint
  2. Review and audit any settings changes made to the system prior to applying the upgrade, as the configuration may have been tampered with
  3. Verify that the settings endpoint now correctly requires admin or superuser privileges before allowing modifications to the global LLM provider configuration
  4. After upgrading, test that unauthenticated users can no longer self-register and access the settings endpoint
  5. Monitor the system for any unusual LLM endpoint configurations that may indicate ongoing exploitation
Caveat Review release notes for 1.2.0 to check for any breaking changes in the upgrade path

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58473 — 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-58473 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