CVE-2026-90768
8.1CAPEv2 · CAPEv2
CAPEv2 contains an authorization vulnerability in REST API endpoints that allows authenticated users to access and delete analysis tasks submitted by other users.
Executive summary
An authorization flaw in the CAPEv2 REST API allows authenticated users to read or delete sensitive analysis data belonging to other users, posing a significant risk to data integrity and confidentiality.
Vulnerability
The application fails to perform proper ownership validation within its REST API task view and delete endpoints. Any authenticated user can bypass intended access controls to enumerate, view, and remove analysis tasks that they do not own.
Business impact
The ability for unauthorized users to access and delete analysis results can lead to the compromise of sensitive malware intelligence and research data. With a CVSS score of 8.1, this vulnerability is classified as High severity, as it facilitates unauthorized data modification and potential loss of proprietary security insights. Unauthorized deletion of these records disrupts incident response workflows and may result in the loss of critical forensics evidence.
Remediation
Immediate Action: Update the CAPEv2 installation to a version beyond commit 471ee4bb422ec4aa0f1aa1089540a1ad0b7d84f0, where ownership validation logic has been implemented.
Proactive Monitoring: Review web server and application access logs for unusual patterns of API requests targeting task IDs, specifically monitoring for frequent DELETE requests or high volumes of GET requests from non-administrative accounts.
Compensating Controls: Implement strict API gateway controls or network level access restrictions to limit access to the REST API to known, trusted IP addresses or specific authenticated service accounts.
Exploitation status
Public Exploit Available: exploit_available (unknown)
Analyst recommendation
Given the High severity of this authorization bypass, organizations should prioritize updating their CAPEv2 deployment immediately to prevent unauthorized data manipulation. Restricting access to the REST API interface through network segmentation is highly recommended until the patch can be verified and applied in production environments.
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
Originally found and disclosed by George Chen, per the CVE Program record.
- GitHub Issue #3162 Issue tracker
- github.com
- Technical analysis
- VulnCheck Advisory: CAPEv2 through commit 471ee4b REST API Task Endpoints Missing Ownership Check Third-party advisory