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-22038: CWE-532: Insertion of Sensitive Information into Log File in Significant-Gravitas AutoGPT

0
High
VulnerabilityCVE-2026-22038cvecve-2026-22038cwe-532
Published: Wed Feb 04 2026 (02/04/2026, 22:28:20 UTC)
Source: CVE Database V5
Vendor/Project: Significant-Gravitas
Product: AutoGPT

Description

CVE-2026-22038 is a high-severity vulnerability in Significant-Gravitas AutoGPT versions prior to autogpt-platform-beta-v0. 6. 46. The issue involves sensitive information leakage where API keys and authentication secrets are logged in plaintext via logger. info() calls in three Stagehand integration blocks. This exposure can lead to confidentiality breaches and potential service disruption. The vulnerability requires low attack complexity but does require some privileges (PR:L) and no user interaction. Although no known exploits are reported in the wild, the impact on confidentiality and availability is significant. The vulnerability has been patched in version 0. 6.

AI-Powered Analysis

AILast updated: 02/04/2026, 22:59:26 UTC

Technical Analysis

CVE-2026-22038 is a vulnerability classified under CWE-532 (Insertion of Sensitive Information into Log File) affecting Significant-Gravitas AutoGPT, a platform enabling continuous AI agents for automating complex workflows. In versions prior to autogpt-platform-beta-v0.6.46, the Stagehand integration components (StagehandObserveBlock, StagehandActBlock, and StagehandExtractBlock) improperly log sensitive data such as API keys and authentication secrets in plaintext using logger.info() statements. Specifically, the code calls api_key.get_secret_value() and outputs these secrets directly into logs, which can be accessed by unauthorized users with log access. This exposure risks confidentiality as attackers can retrieve credentials to escalate privileges or disrupt services. The CVSS 3.1 score of 8.1 reflects high severity, with network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), unchanged scope (S:U), high confidentiality impact (C:H), no integrity impact (I:N), and high availability impact (A:H). The vulnerability has been addressed in autogpt-platform-beta-v0.6.46 by removing or masking sensitive information in logs. No known exploits have been reported in the wild, but the risk remains significant due to the nature of the leaked secrets and potential for misuse.

Potential Impact

For European organizations, this vulnerability poses a serious risk to the confidentiality of API keys and authentication secrets used within AutoGPT deployments. Exposure of these secrets can lead to unauthorized access to AI agents, manipulation of automated workflows, and potential disruption of critical business processes. The high availability impact indicates that attackers could cause service outages or degrade AI-driven operations. Organizations in sectors such as finance, healthcare, manufacturing, and government that increasingly rely on AI automation are particularly vulnerable. Additionally, leaked credentials could be leveraged for lateral movement within networks or to access other integrated systems. The breach of sensitive information may also result in regulatory non-compliance under GDPR, leading to legal and financial penalties. Given the growing adoption of AI platforms in Europe, the threat could affect a broad range of enterprises and public sector entities.

Mitigation Recommendations

European organizations should immediately upgrade all AutoGPT deployments to autogpt-platform-beta-v0.6.46 or later to apply the patch that removes sensitive data from logs. Conduct thorough audits of existing log files to identify and securely purge any logged secrets. Implement strict access controls and monitoring on log storage to prevent unauthorized access. Employ secrets management best practices, such as using environment variables or dedicated vault services, to avoid exposing credentials in application code or logs. Enable logging configurations that redact or mask sensitive information by default. Regularly review and update incident response plans to include procedures for credential leakage scenarios. Additionally, conduct security training for developers and operators to raise awareness about secure logging practices. Organizations should also monitor threat intelligence feeds for any emerging exploits related to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-05T22:30:38.719Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983cbf5f9fa50a62fb2104b

Added to database: 2/4/2026, 10:45:09 PM

Last enriched: 2/4/2026, 10:59:26 PM

Last updated: 2/5/2026, 1:52:08 AM

Views: 5

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