CVE-2026-51867

Deferred Deferred - Pending Action

Incorrect Access Control in AgentGPT Next.js API

Publication date: 2026-09-30

Last updated on: 2026-10-02

Assigner: MITRE

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-30

Last Modified

2026-10-02

Generated

2026-10-19

AI Q&A

2026-10-01

EPSS Evaluated

2026-10-18

NVD

CVE-2026-51867

Affected Vendors & Products

Vendor	Product	Version / Range
agentgpt	agentgpt	1.0.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-284	The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

Executive Summary

This vulnerability in agentgpt v1.0.0 allows unauthorized access to data due to incorrect access control. An exposed API endpoint accepts a user-provided identifier but does not verify ownership or membership, enabling attackers to access sensitive data without proper authorization.

Detection Guidance

To detect CVE-2026-51867, inspect the file next/src/server/api/routers/agentRouter.ts for externally accessible paths that accept object or tenant identifiers without proper ownership or membership validation. Check for missing access control checks on data-access operations.

Impact Analysis

If you use agentgpt v1.0.0, attackers could exploit this flaw to access private data, such as agent configurations or workspace information, without permission. This could lead to data breaches, unauthorized modifications, or exposure of sensitive details.

Compliance Impact

This vulnerability likely violates compliance requirements like GDPR and HIPAA, which mandate strict access controls and data protection. Unauthorized access risks exposing personal or health data, leading to legal penalties, fines, or reputational damage.

Mitigation Strategies

Immediately review and restrict access to the vulnerable path in next/src/server/api/routers/agentRouter.ts. Ensure all data-access operations include proper owner, tenant, workspace, or membership binding checks.

Hi! I’m here to help you understand CVE-2026-51867. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70