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.
CVE-2026-65699
Score 4.2 from GitHub Security Advisory (severity: LOW) published 2026-07-23. a secondary CVSS source baseline 4.2; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EG Score
- 4.2(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 26, 2026AgentGPT 1.0.0 Authorization Bypass via Agent Task Creation | Advisories | VulnCheck
https://www.vulncheck.com/advisories/agentgpt-authorization-bypass-via-agent-task-creationoss/AgentGPT.md at main · geo-chen/oss · GitHub
https://github.com/geo-chen/oss/blob/main/AgentGPT.mdVendor Advisories for CVE-2026-65699(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 20:41 UTCEG score recompute
- 2026-07-28 20:41 UTCGHSA enrichment
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 22:50 UTCEG score recompute
- 2026-07-27 22:50 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 00:57 UTCEG score recompute
- 2026-07-27 00:57 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:07 UTCEG score recompute
- 2026-07-26 03:07 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 17:17 UTCEG score recompute
- 2026-07-23 17:16 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-65699?
When was CVE-2026-65699 disclosed?
Is CVE-2026-65699 actively exploited?
What is the CVSS score of CVE-2026-65699?
How do I remediate CVE-2026-65699?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65699
Is Your Infrastructure Affected by CVE-2026-65699?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.