Autogpt Platform
Approved changes feed: RSS · Atom
cpe:2.3:a:agpt:autogpt_platform:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Agpt (1f783fc9-c798-5fd7-8b08-5e28f17d7f5b) |
|---|---|
| Product | Autogpt Platform (e7dfa3eb-74f7-5dfa-a5f5-d8a44407440c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-26006 |
vulnerable | 2026-06-08 07:53:20.697198 |
Redos (Regular Expression Denial of Service) at Code Extraction Block in significant-gravitas/autogpt
MEDIUM (6.5)
AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. The autogpt before 0.6.32 is vulnerable to Regular Expression Denial of Service due to the use of regex at Code Extraction Block. The two Regex are used containing the corresponding dangerous patterns \s+[\s\S]*? and \s+(.*?). They share a common characteristic — the combination of two adjacent quantifiers that can match the same space character (\s). As a result, an attacker can supply a long sequence of space characters to trigger excessive regex backtracking, potentially leading to a Denial of Service (DoS). This vulnerability is fixed in 0.6.32.
Published: 2026-02-10T21:21:00.635Z
Updated: 2026-02-11T21:27:22.085Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24780 |
vulnerable | 2026-06-08 07:51:18.165366 |
AutoGPT is Vulnerable to RCE via Disabled Block Execution
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.44, AutoGPT Platform's block execution endpoints (both main web API and external API) allow executing blocks by UUID without checking the `disabled` flag. Any authenticated user can execute the disabled `BlockInstallationBlock`, which writes arbitrary Python code to the server filesystem and executes it via `__import__()`, achieving Remote Code Execution. In default self-hosted deployments where Supabase signup is enabled, an attacker can self-register; if signup is disabled (e.g., hosted), the attacker needs an existing account. autogpt-platform-beta-v0.6.44 contains a fix.
Published: 2026-01-29T17:39:33.524Z
Updated: 2026-01-29T21:16:08.779Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22038 |
vulnerable | 2026-06-08 07:49:17.591603 |
AutoGPT's API Keys and Secrets Logged in Plaintext in Stagehand Integration Blocks
HIGH (8.1)
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.46, the AutoGPT platform's Stagehand integration blocks log API keys and authentication secrets in plaintext using logger.info() statements. This occurs in three separate block implementations (StagehandObserveBlock, StagehandActBlock, and StagehandExtractBlock) where the code explicitly calls api_key.get_secret_value() and logs the result. This issue has been patched in autogpt-platform-beta-v0.6.46.
Published: 2026-02-04T22:28:20.401Z
Updated: 2026-02-05T15:04:13.893Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-62616 |
vulnerable | 2026-06-08 07:39:16.219543 |
AutoGPT has SSRF vulnerability in SendDiscordFileBlock
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.
Published: 2026-02-04T22:28:40.783Z
Updated: 2026-02-05T15:01:02.149Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-62615 |
vulnerable | 2026-06-08 07:39:16.218976 |
AutoGPT has SSRF vulnerability in ReadRSSFeedBlock
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 RSSFeedBlock, the third-party library urllib.request.urlopen 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.
Published: 2026-02-04T22:28:37.041Z
Updated: 2026-02-05T15:02:20.452Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-32393 |
vulnerable | 2026-06-08 07:18:59.710680 |
AutoGPT has a DoS vulnerability in ReadRSSFeedBlock
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.32, there is a DoS vulnerability in ReadRSSFeedBlock. In RSSBlock, feedparser.parser is called to obtain the XML file according to the URL input by the user, parse the XML, and finally obtain the parsed result. However, during the parsing process, there is no limit on the parsing time and the resources that can be allocated for parsing. When a malicious user lets RSSBlock parse a carefully constructed, deep XML, it will cause memory resources to be exhausted, eventually causing DoS. This issue has been patched in autogpt-platform-beta-v0.6.32.
Published: 2026-02-05T22:57:54.441Z
Updated: 2026-02-06T19:29:52.815Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-31494 |
vulnerable | 2026-06-08 07:18:57.969744 |
AutoGPT allows cross-user sharing of node execution results through WebSockets API
LOW (3.5)
AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. The AutoGPT Platform's WebSocket API transmitted node execution updates to subscribers based on the graph_id+graph_version. Additionally, there was no check prohibiting users from subscribing with another user's graph_id+graph_version. As a result, node execution updates from one user's graph execution could be received by another user within the same instance. This vulnerability does not occur between different instances or between users and non-users of the platform. Single-user instances are not affected. In private instances with a user white-list, the impact is limited by the fact that all potential unintended recipients of these node execution updates must have been admitted by the administrator. This vulnerability is fixed in 0.6.1.
Published: 2025-04-14T23:21:10.070Z
Updated: 2025-04-15T02:57:00.227Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-31491 |
vulnerable | 2026-06-08 07:18:57.930242 |
AutoGPT allows leakage of cross-domain cookies and protected headers in requests redirect
HIGH (8.6)
AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to 0.6.1, AutoGPT allows of leakage of cross-domain cookies and protected headers in requests redirect. AutoGPT uses a wrapper around the requests python library, located in autogpt_platform/backend/backend/util/request.py. In this wrapper, redirects are specifically NOT followed for the first request. If the wrapper is used with allow_redirects set to True (which is the default), any redirect is not followed by the initial request, but rather re-requested by the wrapper using the new location. However, there is a fundamental flaw in manually re-requesting the new location: it does not account for security-sensitive headers which should not be sent cross-origin, such as the Authorization and Proxy-Authorization header, and cookies. For example in autogpt_platform/backend/backend/blocks/github/_api.py, an Authorization header is set when retrieving data from the GitHub API. However, if GitHub suffers from an open redirect vulnerability (such as the made-up example of https://api.github.com/repos/{owner}/{repo}/issues/comments/{comment_id}/../../../../../redirect/?url=https://joshua.hu/), and the script can be coerced into visiting it with the Authorization header, the GitHub credentials in the Authorization header will be leaked. This allows leaking auth headers and private cookies. This vulnerability is fixed in 0.6.1.
Published: 2025-04-14T23:15:56.611Z
Updated: 2025-04-15T02:58:57.322Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-31490 |
vulnerable | 2026-06-08 07:18:57.929695 |
AutoGPT allows SSRF due to DNS Rebinding in requests wrapper
HIGH (7.5)
AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to 0.6.1, AutoGPT allows SSRF due to DNS Rebinding in requests wrapper. AutoGPT is built with a wrapper around Python's requests library, hardening the application against SSRF. The code for this wrapper can be found in autogpt_platform/backend/backend/util/request.py. The requested hostname of a URL which is being requested is validated, ensuring that it does not resolve to any local ipv4 or ipv6 addresses. However, this check is not sufficient, as a DNS server may initially respond with a non-blocked address, with a TTL of 0. This means that the initial resolution would appear as a non-blocked address. In this case, validate_url() will return the url as successful. After validate_url() has successfully returned the url, the url is then passed to the real request() function. When the real request() function is called with the validated url, request() will once again resolve the address of the hostname, because the record will not have been cached (due to TTL 0). This resolution may be in the "invalid range". This type of attack is called a "DNS Rebinding Attack". This vulnerability is fixed in 0.6.1.
Published: 2025-04-14T23:07:25.840Z
Updated: 2025-04-15T03:00:21.930Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-1040 |
vulnerable | 2026-06-08 07:06:36.692035 |
Server-Side Template Injection (SSTI) in significant-gravitas/autogpt
HIGH (8.8)
AutoGPT versions 0.3.4 and earlier are vulnerable to a Server-Side Template Injection (SSTI) that could lead to Remote Code Execution (RCE). The vulnerability arises from the improper handling of user-supplied format strings in the `AgentOutputBlock` implementation, where malicious input is passed to the Jinja2 templating engine without adequate security measures. Attackers can exploit this flaw to execute arbitrary commands on the host system. The issue is fixed in version 0.4.0.
Published: 2025-03-20T10:11:05.749Z
Updated: 2025-10-15T12:50:50.369Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-0454 |
vulnerable | 2026-06-08 07:02:24.627890 |
SSRF Check Bypass in Requests Utility in significant-gravitas/autogpt
HIGH (7.5)
A Server-Side Request Forgery (SSRF) vulnerability was identified in the Requests utility of significant-gravitas/autogpt versions prior to v0.4.0. The vulnerability arises due to a hostname confusion between the `urlparse` function from the `urllib.parse` library and the `requests` library. A malicious user can exploit this by submitting a specially crafted URL, such as `http://localhost:\@google.com/../`, to bypass the SSRF check and perform an SSRF attack.
Published: 2025-03-20T10:11:30.365Z
Updated: 2025-03-20T15:22:14.163Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.