Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-26006: CWE-1333: Inefficient Regular Expression Complexity in Significant-Gravitas AutoGPT

0
Medium
VulnerabilityCVE-2026-26006cvecve-2026-26006cwe-1333
Published: Tue Feb 10 2026 (02/10/2026, 21:21:00 UTC)
Source: CVE Database V5
Vendor/Project: Significant-Gravitas
Product: AutoGPT

Description

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.

AI-Powered Analysis

AILast updated: 02/18/2026, 09:47:55 UTC

Technical Analysis

CVE-2026-26006 is a vulnerability classified under CWE-1333, involving inefficient regular expression complexity in the Significant-Gravitas AutoGPT platform, specifically versions from 0.4.0 up to 0.6.32. AutoGPT enables users to deploy continuous AI agents to automate complex workflows. The vulnerability stems from two regex patterns used in the Code Extraction Block: "\s+[\s\S]*?" and "\s+(.*?)". Both patterns contain adjacent quantifiers that can match the same whitespace character (\s), leading to catastrophic backtracking when processing long sequences of spaces. An attacker can exploit this by sending specially crafted input containing long whitespace sequences, causing the regex engine to consume excessive CPU resources, resulting in a Denial of Service (DoS). The attack vector is network-based, requiring low privileges and no user interaction, making it relatively easy to exploit remotely. The vulnerability affects availability but does not compromise confidentiality or integrity. The issue was addressed in AutoGPT version 0.6.32, where the regex patterns were presumably optimized or replaced to prevent excessive backtracking. No public exploits are currently known, but the medium CVSS score (6.5) reflects the moderate impact and ease of exploitation. Organizations relying on AutoGPT for AI-driven automation should prioritize patching to avoid service disruptions.

Potential Impact

For European organizations, the primary impact of CVE-2026-26006 is the potential for Denial of Service attacks against AI automation workflows powered by vulnerable AutoGPT versions. Disruptions could affect business-critical processes automated by AI agents, leading to operational downtime and productivity loss. Since the vulnerability does not affect data confidentiality or integrity, the risk of data breaches is low. However, availability issues could cascade into delays in decision-making, customer service interruptions, or failure in automated monitoring systems. Organizations with extensive AI deployments or those integrating AutoGPT into their infrastructure are at higher risk. The ease of exploitation (network accessible, low privileges, no user interaction) increases the likelihood of opportunistic attacks, especially in environments exposed to untrusted inputs. Given the growing adoption of AI automation in sectors like finance, manufacturing, and public services across Europe, the impact could be significant if unpatched.

Mitigation Recommendations

The most effective mitigation is to upgrade AutoGPT to version 0.6.32 or later, where the regex inefficiencies have been resolved. Until upgrading is possible, organizations should implement input validation and sanitization to limit or reject unusually long sequences of whitespace characters in inputs processed by AutoGPT. Network-level protections such as rate limiting, Web Application Firewalls (WAFs), or Intrusion Prevention Systems (IPS) can help detect and block suspicious traffic patterns indicative of ReDoS attempts. Monitoring CPU and memory usage of AutoGPT instances can provide early warning signs of exploitation attempts. Additionally, isolating AutoGPT services in segmented network zones reduces the blast radius of potential DoS attacks. Security teams should review logs for anomalies related to regex processing delays and prepare incident response plans for availability disruptions. Finally, educating developers and operators about safe regex usage and the risks of ReDoS can prevent similar issues in future AI automation projects.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-09T17:41:55.860Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698ba3a54b57a58fa12bb851

Added to database: 2/10/2026, 9:31:17 PM

Last enriched: 2/18/2026, 9:47:55 AM

Last updated: 2/21/2026, 12:18:20 AM

Views: 60

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats