Summary
CVE-2026-51867 is a critical Incorrect Access Control (Insecure Direct Object Reference) vulnerability in AgentGPT, affecting the agentRouter.ts API router in the next component. An externally reachable endpoint accepts caller-supplied object or tenant identifiers and performs data-access operations without validating ownership, tenant binding, or workspace/membership constraints. The flaw carries a CVSS v3.1 base score of 9.8 (Critical) and requires no authentication, privileges, or user interaction to exploit.
Technical details
- Root cause: The
agentRouter.tsAPI router (next/src/server/api/routers/agentRouter.ts) accepts client-supplied object/tenant identifiers and passes them directly into data-access operations without verifying that the requesting caller owns, is a member of, or otherwise has authorization over the referenced resource. - Trigger conditions: A remote, unauthenticated caller sends a request to the affected endpoint specifying an arbitrary identifier for an agent, tenant, or related object.
- Attack vector: Network-based, low attack complexity, no privileges or user interaction required (AV:N/AC:L/PR:N/UI:N).
- Impact: Because resource access is resolved solely from the caller-supplied identifier, an attacker can read, modify, or manipulate data belonging to other users or tenants, resulting in full compromise of confidentiality, integrity, and availability for affected data and operations.
Affected software
- AgentGPT v1.0.0 (component:
next/src/server/api/routers/agentRouter.ts) - No vendor or fixed-version information is currently published; later versions should be checked against the vendor’s repository for a corrective patch.
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: No vendor-confirmed patched version is currently published for this CVE. Monitor the AgentGPT project repository for a fix and upgrade as soon as one is released.
- If no patch is available:
- Restrict external network exposure of AgentGPT instances and the affected API endpoint until a fix is available.
- Place the application behind an authentication and authorization proxy that enforces per-tenant/per-user access checks independent of client-supplied identifiers.
- Audit application logs for requests to agent/tenant endpoints referencing identifiers not belonging to the requesting account.
- Rotate any credentials or secrets potentially exposed through unauthorized data access.

