CVE-2026-67425

Deferred Deferred - Pending Action

Remote Code Execution in Flyto2 Core

Publication date: 2026-07-29

Last updated on: 2026-07-29

Assigner: GitHub, Inc.

Description

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.6, llm.chat reads provider keys such as OPENAI_API_KEY and ANTHROPIC_API_KEY from the environment and sends them in the Authorization: Bearer header to caller-controlled base_url, allowing an attacker to receive the operator's key on a public host that passes the SSRF guard. This issue is fixed in version 2.26.6.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-29

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2026-67425

Affected Vendors & Products

Vendor	Product	Version / Range
flyto2	core	to 2.26.6 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-522	The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
CWE-201	The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Attack-Flow Graph

Executive Summary

Flyto2 Core before version 2.26.6 has a flaw where the llm.chat function reads sensitive API keys like OPENAI_API_KEY and ANTHROPIC_API_KEY from the environment and sends them in an Authorization header to a caller-controlled URL. This allows attackers to intercept these keys via a public host that bypasses SSRF protections.

Detection Guidance

Check if Flyto2 Core versions prior to 2.26.6 are running. Inspect network traffic for outbound Authorization headers containing API keys sent to untrusted base_urls. Review logs for SSRF bypass attempts or unexpected external connections.

Impact Analysis

If exploited, this vulnerability could allow attackers to steal your OpenAI or Anthropic API keys. This could lead to unauthorized use of your AI services, potential financial charges, and exposure of sensitive data processed through these keys.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating GDPR and HIPAA requirements for data protection and confidentiality. Organizations may face legal penalties and reputational damage due to non-compliance.

Mitigation Strategies

Upgrade Flyto2 Core to version 2.26.6 or later. Ensure environment variables like OPENAI_API_KEY and ANTHROPIC_API_KEY are not exposed in logs or network requests. Validate and restrict base_url inputs to prevent SSRF.

Hi! I’m here to help you understand CVE-2026-67425. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70