Cognee
Monthly
Instance-wide LLM configuration hijacking in Cognee before 1.2.0 lets any remote attacker self-register a normal account and overwrite the global LLM provider settings through the /api/v1/settings endpoint, which performs no admin or superuser authorization check. Because the configuration is held in a process-wide singleton cache, a single call redirects every user's LLM operations to an attacker-controlled endpoint, exfiltrating prompts, uploaded documents, extracted entities, and knowledge-graph content. This is confirmed publicly available exploit code exists (reported by VulnCheck, with a released vendor patch in v1.2.0), and the CVSS 4.0 score is 9.3 (Critical).
Authentication token forgery in topoteretes cognee through 1.5.4 lets a remote attacker who can reach the API mint valid JWTs without any account, because the application signs tokens with the publicly known literal "super_secret" whenever the FASTAPI_USERS_JWT_SECRET environment variable is left unset. Because that fallback is the shipped default behavior, unconfigured or default deployments are exposed, and the same pattern affects the password-reset and email-verification token secrets; successful forgery yields full compromise of confidentiality, integrity, and availability of the cognee instance. Upgrading to 1.6.0 removes the shared fallback entirely and replaces it with a per-process random secret; no public exploit code was identified at time of analysis, and CISA KEV does not list this issue.
Instance-wide LLM configuration hijacking in Cognee before 1.2.0 lets any remote attacker self-register a normal account and overwrite the global LLM provider settings through the /api/v1/settings endpoint, which performs no admin or superuser authorization check. Because the configuration is held in a process-wide singleton cache, a single call redirects every user's LLM operations to an attacker-controlled endpoint, exfiltrating prompts, uploaded documents, extracted entities, and knowledge-graph content. This is confirmed publicly available exploit code exists (reported by VulnCheck, with a released vendor patch in v1.2.0), and the CVSS 4.0 score is 9.3 (Critical).
Authentication token forgery in topoteretes cognee through 1.5.4 lets a remote attacker who can reach the API mint valid JWTs without any account, because the application signs tokens with the publicly known literal "super_secret" whenever the FASTAPI_USERS_JWT_SECRET environment variable is left unset. Because that fallback is the shipped default behavior, unconfigured or default deployments are exposed, and the same pattern affects the password-reset and email-verification token secrets; successful forgery yields full compromise of confidentiality, integrity, and availability of the cognee instance. Upgrading to 1.6.0 removes the shared fallback entirely and replaces it with a per-process random secret; no public exploit code was identified at time of analysis, and CISA KEV does not list this issue.