/

CVE-2026-90768

Severity:

HIGH RISK

(8.1)

Authorization Bypass (CWE-862) in CAPEv2 REST API Endpoints

CVE-2026-90768

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Data Access and Analysis Deletion

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

CAPEv2 fails to verify that an authenticated user owns an analysis before allowing access through task view and delete REST API endpoints. As a result, an authenticated attacker may enumerate tasks, read analyses submitted by other users, and delete arbitrary analyses.

Affected context

The vulnerability occurs in CAPEv2 deployments where authenticated users can reach REST API endpoints for viewing or deleting analysis tasks. Risk exists when those endpoints identify tasks by user-supplied identifiers but do not enforce an ownership or equivalent authorization check before returning or removing the associated analysis.

Exploit preconditions

  • Attack surface: CAPEv2 REST API task view and delete endpoints
  • Required access: A valid authenticated user account
  • Trigger point: Requests referencing analysis task identifiers
  • Why exploitation is possible: Endpoint authorization does not confirm that the requesting user owns the targeted task or has an approved administrative role

Why this happens

The underlying bug is an authorization design failure in which authentication is treated as sufficient for access to task resources. The affected endpoints do not consistently apply an ownership check or centralized access-control policy before disclosing or deleting analyses. This maps to CWE-862: Missing Authorization, where a protected operation lacks an effective permission check.

Potential impact

  • An attacker may read analyses belonging to other users
  • Sensitive analysis results or metadata could be disclosed
  • An attacker could delete arbitrary analyses
  • Investigation history and operational records may be disrupted
  • Repeated abuse could reduce trust in analysis data and availability

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every resource access and mutation boundary.

Common defensive patterns include:

  • Applying server-side ownership or role checks to task retrieval and deletion
  • Centralizing authorization decisions so all relevant endpoints use the same policy
  • Denying access by default when ownership or privilege cannot be established
  • Avoiding reliance on client-supplied identifiers as evidence of permission
  • Limiting administrative privileges and separating user and operator capabilities
  • Logging authorization decisions and destructive actions for accountability

These controls should remain effective even when task identifiers are guessed or enumerated.

How teams detect issues like this

Organizations can assess for missing authorization through:

  • Static analysis rules that flag resource access without nearby permission checks
  • Code review of every endpoint that reads, modifies, or deletes user-owned objects
  • Tests using multiple accounts to verify cross-user access isolation
  • Policy checks requiring authorization middleware on protected routes
  • Monitoring for repeated requests involving sequential or unrelated task identifiers

Automated security testing and code review tools may help identify inconsistent access-control enforcement.

Sources

SourceLink
github.comgithub.com/kevoreilly/CAPEv2
github.comgithub.com/kevoreilly/CAPEv2/blob/1255b18/web/apiv2/views.py
github.comgithub.com/kevoreilly/CAPEv2/issues/3162
vulncheck.comvulncheck.com/advisories/capev2-through-commit-471ee4b-rest-api-task-endpoints-missing-ownership-check

Frequently asked

questions

Yes, it may be exploitable through the CAPEv2 REST API when the attacker can reach the affected endpoints and has a valid authenticated account.

The described issue requires authentication. The attacker does not necessarily need administrative privileges if ordinary users can access the vulnerable task endpoints.

Enforce server-side ownership or role-based authorization before every task read and delete operation, using a default-deny policy.

Use centralized authorization middleware, test cross-user access with separate accounts, review destructive endpoints carefully, and monitor access to resources outside a user's permitted scope.

Find out what's already
exploitable in your codebase.