CVE-2026-65699
Deferred Deferred - Pending Action

Authorization Bypass in AgentGPT via User-Controlled Key

Vulnerability report for CVE-2026-65699, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-23

Last updated on: 2026-07-23

Assigner: VulnCheck

Description

AgentGPT through 1.0.0 contains an authorization bypass through user-controlled key vulnerability that allows authenticated users to attach tasks to another user's agent run by supplying a target run_id in the request body without ownership verification. The AgentCRUD.create_task and validate_task_count functions look up the target AgentRun using the client-supplied run_id without confirming the run belongs to the requesting user, enabling an attacker who obtains a valid run_id to corrupt task history, exhaust the per-run loop budget, and drive LLM costs against the victim's run.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-23
Last Modified
2026-07-23
Generated
2026-07-23
AI Q&A
2026-07-23
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
agentgpt agentgpt 1.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-65699 is an authorization bypass vulnerability in AgentGPT through version 1.0.0. It allows authenticated users to attach tasks to another user's agent run by supplying a target run_id in the request body without verifying ownership. The vulnerable functions, AgentCRUD.create_task and validate_task_count, fetch the target AgentRun using the provided run_id without confirming it belongs to the requesting user. This enables attackers with a valid run_id to corrupt task history, exhaust the per-run loop budget, and drive up LLM costs for the victim's run.

Detection Guidance

To detect this vulnerability, inspect AgentGPT logs for unauthorized task attachments or run_id manipulations. Check for requests where users submit run_id values not belonging to them. Look for patterns of task history corruption or unexpected LLM cost spikes. No specific commands are provided in the context, but monitoring API endpoints handling task creation for improper authorization checks may reveal exploitation attempts.

Impact Analysis

This vulnerability could allow an attacker to manipulate your task history, deplete your per-run loop budget, and incur unexpected costs on your account by attaching tasks to your agent run. Since run_id is a UUIDv4, it is not easily guessable, but the lack of ownership checks means the risk exists if an attacker obtains a valid run_id.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by enabling unauthorized access to user data through task manipulation. If an attacker exploits this flaw to alter task history or exhaust resources, it may lead to unauthorized data exposure or processing, violating confidentiality and integrity requirements under these regulations.

Mitigation Strategies

Immediately update AgentGPT to a patched version if available. Implement object-level authorization checks in the agent-task creation path to verify run_id ownership before processing requests. Ensure AgentRun.get() filters by user_id. Review and restrict API endpoints accepting run_id to authenticated users only. Monitor for suspicious task attachments or cost anomalies.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-65699. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart