Quivr versions through 0.0.322 are affected by an authorization bypass flaw that permits authenticated attackers to access and manipulate private chat histories of other users.

This is an authorization bypass vulnerability (CWE-639) occurring because the application fails to validate chat ownership at the API controller level. An authenticated attacker can provide arbitrary chat IDs to the GET, DELETE, and POST endpoints to interact with conversations they do not own.

The ability to read, delete, and inject content into arbitrary chat sessions poses a severe risk to data confidentiality and integrity. If the platform is used for internal knowledge management, sensitive or proprietary information could be exposed to unauthorized parties, leading to potential regulatory noncompliance or reputational damage. With a CVSS score of 8.1, this high-severity vulnerability highlights the significant impact of broken access control in multi-tenant environments.

Immediate Action: Currently, there is no official patch mentioned; users should monitor the Quivr GitHub repository for security updates and apply version 0.0.323 or later as soon as it is released.

Proactive Monitoring: Review application logs for anomalous patterns, specifically looking for repeated 403 errors or unusual access attempts to chat IDs that do not belong to the requesting user session.

Compensating Controls: Implement strict Web Application Firewall (WAF) rules to filter and inspect traffic targeting the /chat/ endpoints, ensuring that requests to sensitive paths are limited to authorized patterns where possible.

Public Exploit Available: No (exploit_available: false)

Given the ease of exploitation and the potential for unauthorized access to private data, organizations should restrict access to the Quivr instance until a vendor-supplied security patch is applied. Administrators must prioritize updating the software as soon as the fix becomes available to remediate this critical authorization flaw.