dbcve.org
Autogpt PlatformApplication · Agpt

CVE-2025-62616

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 0.6.34 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to autogpt-platform-beta-v0.6.34, in SendDiscordFileBlock, the third-party library aiohttp.ClientSession().get is used directly to access the URL, but the input URL is not filtered, which will cause SSRF vulnerability. This issue has been patched in autogpt-platform-beta-v0.6.34.

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

AutoGPT platform's SendDiscordFileBlock function makes HTTP requests via aiohttp.ClientSession().get using user-supplied URLs without any validation or sanitization. This allows attackers to craft malicious URLs that cause the server to make requests to internal infrastructure, cloud metadata endpoints, or other sensitive internal services, leading to SSRF.

MitigationUpgrade to autogpt-platform-beta-v0.6.34 or later. If immediate patching is not possible, implement URL allowlist validation and disable requests to internal/private IP ranges before passing URLs to aiohttp.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Autogpt PlatformApplication
Affected:< 0.6.34

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check installed AutoGPT platform version
    Run `pip show autogpt-platform` or check your package.json for the autogpt-platform version number
    Affected if Version is below 0.6.34 (e.g., 0.6.0, 0.5.x, etc.)
  2. Identify if SendDiscordFileBlock is in use
    Search your codebase for imports or references to 'SendDiscordFileBlock' or 'discord' related modules, or check your workflow configurations for Discord integration blocks
    Affected if The SendDiscordFileBlock function or Discord file upload feature is enabled or used in workflows
  3. Verify URL validation exists in the codebase
    Search the codebase for URL validation logic near the aiohttp.ClientSession usage, specifically looking for allowlists, URL sanitization, or SSRF protections
    Affected if No URL validation or allowlist logic is found before the aiohttp.ClientSession().get call
  4. Check for internal network restrictions on HTTP requests
    Inspect any proxy configuration, firewall rules, or application network policies that may restrict outbound requests from the AutoGPT service
    Affected if No network restrictions are configured to block requests to internal IP ranges (e.g., 127.0.0.1, 169.254.169.254, 10.0.0.0/8)
  5. Review environment for exposed cloud metadata endpoints
    Confirm whether the AutoGPT service runs in a cloud environment where metadata endpoints (such as AWS169.254.169.254, GCP metadata.google.internal) are accessible from the service's network
    Affected if The service runs in a cloud environment with accessible metadata endpoints and no IP-based restrictions

You are affected if you run any AutoGPT platform version below 0.6.34 and use the SendDiscordFileBlock feature without URL validation or network restrictions, allowing attackers to trigger internal service requests via crafted URLs.

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
Upgrade available Upgrade to 0.6.34 or later
Fixed in 0.6.34
Interim mitigation

Upgrade to autogpt-platform-beta-v0.6.34 or later. If immediate patching is not possible, implement URL allowlist validation and disable requests to internal/private IP ranges before passing URLs to aiohttp.

Recommended fix High confidence

autogpt-platform-beta-v0.6.34

  1. 1. Identify the AutoGPT Platform installation directory
  2. 2. Locate the current version being used (should be below 0.6.34)
  3. 3. Upgrade the AutoGPT Platform to version autogpt-platform-beta-v0.6.34 or later
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Test the SendDiscordFileBlock functionality to ensure it still works correctly

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

Fix this in Autogpt Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62616 — 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-2025-62616 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