CVE-2026-56663

Home/CVE/AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agent

CVE

↯ PDF report

AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agent

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.

HIGH · CVSS 8.5

Schedule remediation

CVSS base score ≥ 7.0

No Sigma yet — build one → YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2026-56663, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

⚠

Exploitation evidence

1 of 7 sources

Corroboration score 8/100 · emerging. This counts how many independent sources have exploitation evidence, and separates two different things: confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.

Exploit / PoC available

public PoC

▣

Severity & exploitation scoring

View on NVD →

CVSS base score

8.5

HIGHCVSS v3.1 · [email protected]

EPSS exploitation probability

n/a

No EPSS score in our data for this CVE. EPSS is published daily for scored CVEs - a very new, reserved, or rejected CVE may not have one yet.

CVSS metric silhouette

shape grows toward worst-case

SSVC triage · cisa-vulnrichment

Exploitation

poc

Automatable

Tech impact

total

CVSS vector breakdown

Exploitability - how they get in

Attack Vector

Network Adjacent Local Physical

Attack Complexity

Low High

Privileges Required

None Low High

User Interaction

None Required

Scope

Unchanged Changed

Impact - what breaks

Confidentiality

None Low High

Integrity

None Low High

Availability

None Low High

VECTORCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Attack path

Full kill chain

→

◆

ATT&CK techniques

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1090 · Proxy

▤ Build a SIEM detection for these techniques