What is the CVSS score of CVE-2026-22038?

CVE-2026-22038 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2026-22038?

Yes, a public proof-of-concept exploit is available for CVE-2026-22038. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2026-22038?

Within 24 hours: Inventory all AutoGPT deployments and assess current patch status; notify affected teams to monitor for suspicious agent behavior. Within 7 days: Apply the available vendor patch to all AutoGPT instances in a phased approach, prioritizing production environments. Within 30 days: Complete patching of all remaining instances, conduct security testing to confirm vulnerability remediation, and document patch deployment status for audit purposes.

Autogpt Platform CVE-2026-22038

HIGH

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

2026-02-04 security-advisories@github.com

Information Disclosure AI / ML Autogpt Platform Agpt

8.1

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticate to AutoGPT platform
Exploit

Access workflow containing Stagehand block
Execution

Trigger block execution
Impact

Extract plaintext API keys from logs

Vulnerability Assessment

Weakness	CWE CWE-532 OWASP Top 10:2025 A09:2025 - Security Logging & Alerting Failures ASVS 5.0 V16 - Security Logging and Error Handling Log data sanitization
Exploitation Conditions	Authenticated user access to AutoGPT platform with permission to deploy workflows using StagehandObserveBlock, StagehandActBlock, or StagehandExtractBlock before version v0.6.46. Requires ability to view application logs containing logged secrets.
Impact	CVSS 8.1 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: None. Public exploit/POC available.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to create, deploy, and manage continuous artificial intelligence agents that automa.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

AutoGPT platform versions prior to v0.6.46 expose API keys and authentication secrets in application logs due to insecure logging of decrypted credentials across three Stagehand integration blocks. Authenticated users can access these plaintext secrets through log files, enabling credential theft and unauthorized access to integrated services. Public exploit code exists for this vulnerability, though a patch is available in v0.6.46 and later.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:54 CVSS 8.1

AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. [CVSS 8.1 HIGH]

RemediationAI

A vendor patch is available — apply it immediately. Restrict network access to the affected service where possible.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-532 (Insertion of Sensitive Information into Log File). Affects Autogpt Platform. 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

Know when Autogpt Platform gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 8.1 HIGH

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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Lifecycle Timeline

PoC Detected

Feb 17, 2026 - 15:42 vuln.today

Public exploit code

Patch released

Feb 17, 2026 - 15:42 nvd

Patch available

CVE Published

Feb 04, 2026 - 23:15 nvd

HIGH 8.1

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

A HIGH severity vulnerability (CVE-2026-22038) affecting AutoGPT poses a significant risk to organizations using this platform for AI agent automation. With a CVSS score of 8.1 and public exploits already available, threat actors can potentially compromise AI workflows and sensitive automation processes. Immediate patching is critical to prevent unauthorized access or manipulation of automated business operations.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.1%

Top 73% exploitable

Exploit

POC

Public exploit code exists

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +40

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.