Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to AutoGPT Platform
-
DeliveryCreate agent using SendWebRequestBlock
-
ExploitPoint URL at attacker hostname resolving to IPv4-mapped/CGNAT address
-
ExecutionBypass _is_ip_blocked() deny list
-
PersistBackend connects to internal IPv4 endpoint
-
ImpactExfiltrate internal/metadata service data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated AutoGPT Platform account (PR:L) with the ability to create or run an agent that uses the SendWebRequestBlock. The attacker must supply a hostname that resolves to an IPv4-mapped IPv6 address (e.g. ::ffff:<internal IPv4>) or to an address in the RFC 6598 CGNAT range 100.64.0.0/10 - both of which the unpatched _is_ip_blocked() fails to block. Limiting factors: exploitation is gated by authentication, by needing control over DNS resolution for the chosen hostname (contributing to AC:H), and by the existence of reachable internal IPv4 services worth targeting; impact is bounded by what those internal endpoints expose. All versions before 0.6.52 in default configuration are affected, so no special non-default product setting is needed beyond access to the request block. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, base 8.5 High) reflects a network-reachable, authenticated SSRF with changed scope, the high score driven largely by the scope change and assumed full triad impact on reachable internal systems. AC:H is appropriate: the attacker must control or craft a hostname whose DNS resolution returns an IPv4-mapped IPv6 (or CGNAT) address, which is non-trivial but well within the means of a determined actor controlling their own DNS. PR:L means a valid platform account is required, narrowing the population to tenants/users who can already create or run agent workflows. No KEV listing and no POC are present in the supplied intelligence, and no EPSS score was provided, so there is no signal of active or imminent mass exploitation - this is a real, credible internal-pivot bug rather than a confirmed in-the-wild threat. Note one tension to verify: the I:H/A:H ratings imply the attacker can write/disrupt internal services, but an SSRF's actual integrity/availability impact depends entirely on what internal endpoints exist and whether they accept state-changing requests, so the real impact may be lower than the vendor base score suggests. |
| Exploit ScenarioDerived | An attacker with a valid AutoGPT account creates an agent that uses the SendWebRequestBlock and points it at a hostname under their control whose DNS record resolves to an IPv4-mapped IPv6 address (e.g. ::ffff:169.254.169.254 or a 100.64.x.x CGNAT address). The deny-list check fails to canonicalize the address, so the request bypasses the SSRF filter and the backend connects to the internal endpoint, letting the attacker query cloud metadata services or internal-only APIs. No public POC is identified, but the high attack complexity (controlling DNS resolution to a mapped address) is the main practical barrier. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 26, 2026
Server-side request forgery in the AutoGPT Platform (versions prior to 0.6.52) lets an authenticated user abuse the SendWebRequestBlock to reach internal network services that the private-IP filter is supposed to protect. The flaw stems from _is_ip_blocked() in backend/backend/util/request.py failing to normalize IPv4-mapped IPv6 addresses and omitting RFC 6598 CGNAT space (100.64.0.0/10), so a hostname resolving to a mapped address passes validation and the request hits the embedded internal IPv4 endpoint. No public exploit identified at time of analysis; this affects all AutoGPT Platform deployments and is fixed in 0.6.52.
RemediationAI
Upgrade to AutoGPT 0.6.52, which contains the fix (Vendor-released patch: 0.6.52) - this version normalizes IPv4-mapped IPv6 addresses before the deny-list check and blocks the RFC 6598 100.64.0.0/10 CGNAT range. Until upgrade is possible, compensating controls include restricting who holds authenticated accounts that can create or execute agents containing the SendWebRequestBlock (the bug requires PR:L), and disabling or removing the SendWebRequestBlock / outbound-fetch capability if it is not needed - the trade-off is loss of any legitimate HTTP-fetch automation. At the network layer, place the AutoGPT backend behind an egress proxy or firewall that whitelists only required external destinations and denies traffic to internal/link-local/CGNAT ranges (127.0.0.0/8, 169.254.0.0/16, 10/8, 172.16/12, 192.168/16, 100.64.0.0/10) including their IPv6-mapped forms; the side effect is that legitimate agents needing broad internet access must be explicitly allowlisted. The authoritative advisory is https://github.com/Significant-Gravitas/AutoGPT/security/advisories/GHSA-8qc5-rhmg-r6r6.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
AutoGPT is an open-source workflow-automation platform for building and running autonomous AI agents. The vulnerable component is the SendWebRequestBlock, an agent action that fetches arbitrary URLs; to prevent SSRF it resolves the target hostname and checks the resulting IPs against blocked private/reserved IPv4 ranges in _is_ip_blocked() (backend/backend/util/request.py). This is a classic CWE-918 (Server-Side Request Forgery) deny-list bypass: the validator does not canonicalize IPv4-mapped IPv6 addresses (e.g. ::ffff:127.0.0.1 / ::ffff:169.254.x.x) back to their embedded IPv4 form before comparison, and it omits the RFC 6598 carrier-grade NAT range 100.64.0.0/10. Because the dual-stack socket layer ultimately connects to the embedded IPv4 endpoint, a hostname engineered to resolve to a mapped or CGNAT address slips past the deny list. The affected product per CPE is cpe:2.3:a:significant-gravitas:autogpt:*, with all versions before 0.6.52 vulnerable.
Know when Autogpt gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Authenticated user (PR:L) must craft DNS to a mapped/CGNAT address (AC:H); SSRF reaches internal systems (S:C) primarily exposing data (C:H), with limited integrity and no inherent availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Prior to 0.6.52, an authenticated user can bypass the SSRF / private-IP protections in SendWebRequestBlock and reach internal network services. _is_ip_blocked() in backend/backend/util/request.py does not normalize IPv4-mapped IPv6 addresses before checking resolved IPs against the blocked IPv4 ranges, and does not block special-use ranges such as 100.64.0.0/10 (CGNAT, RFC 6598). A hostname that resolves to an IPv4-mapped IPv6 address therefore passes validation and the request reaches the embedded internal IPv4 endpoint. This affects all AutoGPT Platform deployments. This vulnerability is fixed in 0.6.52.
Executive ViewAI
AutoGPT Platform versions before 0.6.52 contain a server-side request forgery vulnerability that allows authenticated users to bypass internal network security controls and access sensitive backend infrastructure, creating risk of data exposure and lateral movement. All AutoGPT Platform deployments are affected and require immediate patching.
Apply vendor patch: AutoGPT Platform version 0.6.52
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
DOM-based cross-site scripting in AutoGPT versions prior to 0.6.62 allows remote attackers to execute arbitrary JavaScri
Resource exhaustion denial-of-service in Significant Gravitas AutoGPT versions prior to 0.6.63 allows remote unauthentic
Denial of service in Significant-Gravitas AutoGPT prior to 0.6.63 allows remote attackers to exhaust host disk space by
Denial of service in AutoGPT prior to 0.6.63 allows remote unauthenticated users to exhaust host disk space by chaining
Denial of service in AutoGPT versions prior to 0.6.63 allows remote unauthenticated attackers to exhaust disk space on t
Webhook signature verification bypass in AutoGPT Platform before 0.6.70 allows unauthenticated remote attackers to trigg
Insecure deserialization in Significant-Gravitas AutoGPT platform versions 0.6.34 through 0.6.51 lets an attacker who ca
Unauthenticated denial-of-service in AutoGPT Platform versions 0.4.2 through 0.6.51 allows remote attackers to exhaust s
Disk exhaustion denial-of-service in Significant Gravitas AutoGPT prior to version 0.6.63 allows authenticated platform
Authenticated session hijacking in Significant Gravitas AutoGPT versions 0.6.36 through 0.6.50 allows any logged-in user
Improper access control in AutoGPT’s webhook ping endpoint allows any authenticated user to enumerate other users’ webho
Memory exhaustion in AutoGPT's AITextSummarizerBlock allows authenticated users to trigger extreme resource amplificatio
EUVD-2026-39798
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB