dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-33234

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. In versions 0.1.0 through 0.6.51, SendEmailBlock in autogpt_platform/backend/backend/blocks/email_block.py accepts a user-supplied smtp_server (string) and smtp_port (integer) as per-execution block inputs, then passes them directly to Python's smtplib.SMTP() to open a raw TCP connection with no IP address validation. This completely bypasses the platform's hardened SSRF protections in backend/util/request.py — the validate_url_host() function and BLOCKED_IP_NETWORKS blocklist that every other block uses to block connections to private, loopback, link-local, and cloud metadata addresses. An authenticated user on a shared AutoGPT deployment can use this to perform non-blind internal network port scanning and service fingerprinting: smtplib reads the target's TCP banner on connect and embeds it in the exception message, which is persisted as user-visible block output via the execution framework. This issue has been fixed in version 0.6.52.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SendEmailBlock in AutoGPT accepts user-supplied SMTP server and port as execution inputs, passing them directly to smtplib.SMTP() without validating the target IP address. This bypasses the platform's existing SSRF protections (validate_url_host() and BLOCKED_IP_NETWORKS), allowing authenticated users to connect to arbitrary internal network services, perform port scanning, and retrieve TCP banners that reveal service fingerprints.

MitigationUpgrade to AutoGPT version 0.6.52 or later, which includes IP address validation for the SendEmailBlock inputs. Alternatively, implement input validation matching the platform's existing validate_url_host() function before passing SMTP parameters to smtplib.SMTP().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AutoGPT version
    Run 'pip show autogpt' or check the package version in your dependency management system (e.g., pyproject.toml, requirements.txt)
    Affected if Version is 0.1.0 through 0.6.51 (inclusive)
  2. Locate SendEmailBlock implementation
    Search the codebase for 'class SendEmailBlock' or the file containing the email block functionality, typically in the blocks or workflow modules
    Affected if The SendEmailBlock code exists and accepts SMTP server/port parameters directly without calling validate_url_host()
  3. Verify SMTP parameter handling
    Inspect the SendEmailBlock code: look for smtplib.SMTP() calls and check if the server/port arguments pass through validate_url_host() or check against BLOCKED_IP_NETWORKS before use
    Affected if SMTP server and port are passed directly to smtplib.SMTP() without IP validation against the blocklist
  4. Confirm user access to SendEmailBlock
    Check if authenticated users can access or configure the SendEmailBlock in workflows, automations, or as part of agent actions
    Affected if The SendEmailBlock is enabled and accessible to users who can supply custom SMTP server addresses
  5. Test for exception message information disclosure
    If SendEmailBlock is in use, attempt to provide an internal IP (e.g., 127.0.0.1, 192.168.x.x) as the SMTP server and observe whether exception messages reveal TCP banner responses or service information
    Affected if Exception messages expose internal service fingerprints or connection details when invalid internal hosts are provided

Your environment is affected if AutoGPT version is 0.1.0-0.6.51 and the SendEmailBlock is accessible to users without IP validation on the SMTP server parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to AutoGPT version 0.6.52 or later, which includes IP address validation for the SendEmailBlock inputs. Alternatively, implement input validation matching the platform's existing validate_url_host() function before passing SMTP parameters to smtplib.SMTP().

Recommended fix High confidence

0.6.52

  1. Upgrade AutoGPT from any version between 0.1.0 and 0.6.51 to version 0.6.52 or later to resolve the SSRF vulnerability in SendEmailBlock

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33234 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33234 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data