VulnerabilityPublished 19 May 2026

CVE-2026-33234: Significant-Gravitas AutoGPT · Server-Side Request Forgery (SSRF)

Affects Significant-Gravitas AutoGPTSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 0.6.52 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.6.52

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Significant-Gravitas AutoGPT to 0.6.52.

Affected software

Product	Affected	Fixed in
Significant-GravitasAutoGPT	Affected >=0.1.0 <0.6.52	Fixed in 0.6.52
PyPIautogpt`pkg:pypi/autogpt`Other threats	Affected =0.1.0 <=0.6.51	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability has been fixed in AutoGPT version 0.6.52. Users should upgrade to version 0.6.52 or later to remediate this issue. Since the vendor advisory does not provide an official patch link or alternative mitigations, upgrading to the fixed version is the recommended action. Patch status is confirmed by the version fix note in the description.

Description

CVE-2026-33234 is a Server-Side Request Forgery (SSRF) vulnerability in Significant-Gravitas AutoGPT versions 0.1.0 through 0.6.51. The vulnerability arises because the SendEmailBlock accepts user-supplied SMTP server and port inputs and passes them directly to Python's smtplib. SMTP() without IP address validation. This bypasses the platform's usual SSRF protections, allowing an authenticated user on a shared deployment to perform internal network port scanning and service fingerprinting. The issue was fixed in version 0.6.

Impact

An authenticated user on a shared AutoGPT deployment can exploit this SSRF vulnerability to perform internal network port scanning and service fingerprinting. This could potentially reveal information about internal services and network topology. The vulnerability does not directly allow data confidentiality or integrity compromise but leaks service banners via exception messages. There are no known exploits in the wild as of the published date.

Summary

AutoGPT is a workflow automation platform for AI agents. In versions 0.1.0 to 0.6.51, the SendEmailBlock component accepts user inputs for smtp_server and smtp_port, which are then used directly in Python's smtplib.SMTP() to establish TCP connections without validating the IP address. This bypasses the platform's hardened SSRF protections that normally block connections to private, loopback, link-local, and cloud metadata addresses. As a result, an authenticated user can leverage this to conduct internal network port scanning and fingerprint services by reading TCP banners returned in exception messages. The vulnerability is classified as CWE-918 and has a CVSS v3.1 base score of 5.0 (medium severity). It was fixed in AutoGPT version 0.6.52.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 May 2026, 08:24 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats