CVE-2026-51916 in SuperAGI
Summary
by MITRE • 10/02/2026
TransformerOptimus SuperAGI v0.0.14 contains an incorrect access control vulnerability in delete_user_knowledge in superagi/controllers/knowledges.py. In affected source snapshots, POST /knowledges/delete/{knowledge_id} deletes the selected knowledge object without requiring authentication in the route and without verifying organization ownership of the supplied knowledge_id.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 10/02/2026
The identified vulnerability represents a critical failure in access control mechanisms within TransformerOptimus SuperAGI version 0.0.14, specifically located in the delete_user_knowledge function found in superagi/controllers/knowledges.py. This flaw allows an unauthenticated attacker to permanently remove knowledge objects associated with specific users or organizations by exploiting the POST /knowledges/delete/{knowledge_id} endpoint. The core technical deficiency lies in two distinct areas: the absence of authentication requirements for the route and the lack of authorization checks regarding organization ownership. Consequently, any individual on the network can invoke this API call without providing valid credentials, bypassing standard security gateways that typically enforce identity verification before processing sensitive data modification requests.
From a technical perspective, the vulnerability stems from improper implementation of role-based access control principles within the application logic. The endpoint does not validate whether the requester has the necessary permissions to perform deletion operations on the specified resource. Furthermore, it fails to verify if the knowledge_id provided in the request actually belongs to an organization or user that is authorized by the requesting entity. This oversight creates a scenario where arbitrary data destruction can occur without any form of accountability or audit trail related to identity verification. The application treats all incoming deletion requests as valid regardless of their source, which fundamentally undermines the integrity and confidentiality guarantees expected in multi-tenant environments.
The operational impact of this vulnerability is severe, primarily affecting data integrity and availability within the SuperAGI platform. Attackers can exploit this flaw to delete critical knowledge bases that may contain valuable intellectual property, training data, or sensitive organizational information. Since there are no authentication barriers, even external adversaries who have discovered the API endpoint structure can execute these destructive actions remotely. This leads to potential loss of business continuity and significant reputational damage for organizations relying on SuperAGI for their artificial intelligence workflows. The inability to trace deletions back to specific authenticated users also complicates forensic investigations following an incident, as there is no clear attribution mechanism tied to the deletion events.
This vulnerability aligns with CWE-284 Improper Access Control and CWE-798 Use of Hard-coded Credentials if authentication bypass relies on default configurations, though primarily it reflects a failure in object-level authorization checks often categorized under CWE-862 Missing Authorization. In terms of offensive security frameworks, this behavior corresponds to ATT&CK technique T1078 Valid Accounts when considering the potential for privilege escalation through unauthenticated access, and more accurately maps to data destruction activities seen in techniques like T1485 Data Destruction or T1499 Endpoint Denial of Service if used maliciously at scale. The lack of ownership verification specifically highlights a gap in enforcing proper resource isolation between different tenants or user groups within the application architecture.
To mitigate this vulnerability, immediate remediation efforts should focus on implementing robust authentication and authorization checks for all API endpoints that modify data state. Developers must ensure that every request to delete_user_knowledge requires valid session tokens or API keys associated with an authenticated user identity. Additionally, strict ownership verification logic must be integrated into the controller method to confirm that the knowledge_id being deleted belongs exclusively to the organization or user making the request. Implementing comprehensive logging and monitoring for deletion events will also aid in detecting potential abuse attempts early. Regular security code reviews focusing on access control patterns are recommended to prevent similar flaws from emerging in other parts of the application, ensuring adherence to secure coding standards such as OWASP API Security Top Ten guidelines regarding broken object level authorization protections.