CVE-2026-90579

7.3

cheshire-cat-ai · Cheshire Cat AI

Cheshire Cat AI up to 1.9.2 fails to validate user identity in default configurations, allowing unauthenticated attackers to impersonate any user via a manipulated HTTP header.

Executive summary

A critical authentication bypass vulnerability in Cheshire Cat AI allows unauthenticated remote attackers to assume any user identity and access sensitive data due to improper credential verification.

Vulnerability

The application incorrectly trusts a client-supplied user_id HTTP header when no API key is configured. This missing authentication flaw allows any unauthenticated remote attacker to gain full permissions for any user account by simply injecting the target identifier into the request headers.

Business impact

This vulnerability poses a severe risk of unauthorized data access and total loss of confidentiality for all user accounts within the Cheshire Cat AI platform. An attacker can read conversation histories and access episodic memory without any form of authentication, leading to significant privacy violations and potential exposure of sensitive organizational information. Given the CVSS score of 7.3, this issue represents a high-severity threat that can be exploited easily by any network-adjacent actor.

Remediation

Immediate Action: As no official patch is currently available, administrators must immediately secure the installation by manually configuring a strong, unique API key (CCAT_API_KEY) to disable the insecure default behavior.

Proactive Monitoring: Review web server and application access logs for requests containing suspicious or unexpected user_id headers, particularly those originating from unauthorized or external IP addresses.

Compensating Controls: Deploy a Web Application Firewall (WAF) to inspect incoming traffic and block requests that contain unauthorized or malformed user_id headers, effectively restricting access to the application until a permanent fix is applied.

Exploitation status

Public Exploit Available: Yes — a published proof-of-concept exists, attributed to the security researcher's write-up on GitHub (Issue #1137).

Analyst recommendation

The absence of a vendor-provided patch necessitates immediate manual intervention to protect the environment. Administrators should verify their current deployment settings and enforce API key authentication without delay to prevent unauthorized access. Given that the vulnerability is publicly documented and requires no specialized exploitation skills, the risk of compromise is high for any exposed instance of Cheshire Cat AI.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by geochen (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.