CyberSecBulletin
CVE-2026-22038NVD status: Analyzed

AutoGPT: Insertion of Sensitive Information into Log File

CVE-2026-22038 is a high-severity insertion of sensitive information into log file vulnerability in AutoGPT from Significant-Gravitas, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected AutoGPT versions: < autogpt-platform-beta-v0.6.46. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.49% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Autogpt Platform to 0.6.46 or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Significant-GravitasAutoGPT< autogpt-platform-beta-v0.6.46Not stated
AgptAutogpt Platformbefore 0.6.460.6.46

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by CNA (github.com).

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in AutoGPT

All AutoGPT vulnerabilities

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.