CVE-2026-65699: Authorization Bypass Through User-Controlled Key in reworkd AgentGPT
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.
AI Analysis
Technical Summary
CVE-2026-65699 is an authorization bypass vulnerability in reworkd's AgentGPT product through version 1.0.0. The issue occurs because the application accepts a user-supplied run_id in the request body to attach tasks to an agent run but fails to verify that the run_id belongs to the authenticated user making the request. This lack of ownership verification in the AgentCRUD.create_task and validate_task_count functions enables an attacker who obtains a valid run_id to interfere with another user's agent run by corrupting task history, exhausting the run's loop budget, and driving up costs associated with the large language model (LLM) usage on the victim's account.
Potential Impact
An attacker with a valid run_id can manipulate another user's agent run by attaching unauthorized tasks. This can lead to corrupted task histories, depletion of the allowed loop budget per run, and increased operational costs for the victim due to excessive LLM usage. The CVSS 4.0 base score is 2.3, indicating a low severity impact primarily due to the requirement for authenticated access and high attack complexity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to valid run_ids and monitor for unusual task attachment activity. Users should avoid sharing run_ids and ensure that only authorized users have authenticated access. Follow vendor updates for official patches or fixes.
CVE-2026-65699: Authorization Bypass Through User-Controlled Key in reworkd AgentGPT
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 v4.0
Score 2.3low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-65699 is an authorization bypass vulnerability in reworkd's AgentGPT product through version 1.0.0. The issue occurs because the application accepts a user-supplied run_id in the request body to attach tasks to an agent run but fails to verify that the run_id belongs to the authenticated user making the request. This lack of ownership verification in the AgentCRUD.create_task and validate_task_count functions enables an attacker who obtains a valid run_id to interfere with another user's agent run by corrupting task history, exhausting the run's loop budget, and driving up costs associated with the large language model (LLM) usage on the victim's account.
Potential Impact
An attacker with a valid run_id can manipulate another user's agent run by attaching unauthorized tasks. This can lead to corrupted task histories, depletion of the allowed loop budget per run, and increased operational costs for the victim due to excessive LLM usage. The CVSS 4.0 base score is 2.3, indicating a low severity impact primarily due to the requirement for authenticated access and high attack complexity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to valid run_ids and monitor for unusual task attachment activity. Users should avoid sharing run_ids and ensure that only authorized users have authenticated access. Follow vendor updates for official patches or fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-22T20:26:09.980Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a624de29c2644c7f86dab97
Added to database: 07/23/2026, 17:22:42 UTC
Last enriched: 07/23/2026, 17:37:47 UTC
Last updated: 07/23/2026, 21:06:59 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.