AgentGPT: Incorrect access control in agentRouter API
Summary
AgentGPT v1.0.0 contains an incorrect access control flaw in the Next.js router agentRouter.ts. An externally reachable path accepts a caller-selected object or tenant identifier and runs a data-access operation without checking that the object belongs to the caller's owner, tenant, workspace or membership. Per the CVE record, an attacker may be able to read data of other users or tenants, for example tasks and goals of an agent. The CVSS vector given with the request is PR:N (no privileges required), but this is not confirmed by NVD, and the public analysis refers to an authenticated caller, so the actual exposure depends on the deployment.
Affected
- AgentGPT v1.0.0 (according to the CVE description)
- Other versions: Unknown.
Fixed in
Unknown. No vendor advisory or fixed release was found. The project appears to be archived or unmaintained.
Workaround
- Do not expose the instance to the internet; use a VPN or an identity-aware proxy.
- Limit accounts to required users and remove unused accounts.
- Do not store sensitive or cross-client data in the instance until ownership checks are reviewed.
- Apply an ownership check in the router (verify the relationship between the authenticated user and the requested resource ID) or retire the deployment.
- Monitor application logs for unusual object or tenant identifiers in API calls.
Exploitation
- CISA SSVC assessment: exploitation status PoC, automatable: yes, technical impact: total.
- A public GitHub gist with reproduction notes is referenced; its content has not been verified.
- No known exploitation in the wild; not listed in the CISA KEV catalog (as far as checked).
Our recommendation
- Check whether any AgentGPT 1.0.0 instance is running, especially internet-facing or multi-user instances.
- Remove the instance from public access immediately or retire it if it is not needed.
- Review application and access logs for unusual object or tenant identifiers.
- Consider the software unmaintained and plan a replacement or a reviewed fork with fixed ownership checks.
- Confirm the official CVSS score and CWE in NVD.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- CVE-2026-51867 Gist (Researcher) gist.github.com
- VulDB: CVE-2026-51867 vuldb.com
- Strix: CVE-2026-51867 www.strix.ai
- OffSeq Radar: CVE-2026-51867 radar.offseq.com
- TheHackerWire: CVE-2026-51867 www.thehackerwire.com
- DeepWiki: reworkd/AgentGPT deepwiki.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 30 Oct 2026, 21:42.
Original description (NVD)
agentgpt v.1.0.0 is vulnerable to Incorrect Access Control in next/src/server/api/routers/agentRouter.ts. An externally reachable path accepts a caller-selected object or tenant identifier and reaches a data-access operation without a visible owner, tenant, workspace, or membership binding on that object.
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.