Skip to content
AI/ML

CVE-2026-58473

9.3
Critical
EPSS 0.51%Patch availableJul 8, 2026

Unauthenticated actors can overwrite global LLM provider, enabling instance-wide data exfiltration.

common questions

Is CVE-2026-58473 being exploited?

Not confirmed. CVE-2026-58473 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-58473?

CVE-2026-58473 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58473?

Yes. A fix has been recorded for CVE-2026-58473. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58473 affect?

CVE-2026-58473 affects Cognee < 1.2.0, Self-hosted Cognee instances, Instances using Cognee LLM integrations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58473?

Upgrade to Cognee >=1.2.0, restrict self-registration, audit/rotate LLM keys

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Cognee < 1.2.0Self-hosted Cognee instancesInstances using Cognee LLM integrations
impact

Unauthenticated attacker can change the global LLM endpoint to an attacker-controlled server, exfiltrating prompts, uploaded docs, extracted entities and knowledge graph content from all users.

action required

Immediate action required

affected versions
topoteretes cognee
  • affected< 1.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free