CVE-2026-67425: CWE-201: Insertion of Sensitive Information Into Sent Data in flytohub flyto-core
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.
AI Analysis
Technical Summary
Flyto-core versions before 2.26.6 contain a vulnerability where the llm.chat module reads sensitive environment variables containing provider API keys and includes them in the Authorization: Bearer header when making requests to a base_url controlled by the caller. This behavior allows an attacker to receive these sensitive keys if they can direct requests to a public host that circumvents the server-side request forgery (SSRF) guard. The vulnerability is classified under CWE-201 (Insertion of Sensitive Information Into Sent Data) and CWE-522 (Insufficiently Protected Credentials). The issue is resolved in flyto-core version 2.26.6.
Potential Impact
An attacker who can control the base_url parameter and direct requests to a public host that bypasses SSRF protections can obtain sensitive API keys (e.g., OPENAI_API_KEY, ANTHROPIC_API_KEY) from the environment. This exposure can lead to unauthorized use of these keys, potentially resulting in data breaches or abuse of the associated AI services. The vulnerability does not affect integrity or availability directly but results in a high confidentiality impact.
Mitigation Recommendations
This vulnerability is fixed in flyto-core version 2.26.6. Users should upgrade to version 2.26.6 or later to remediate this issue. Since no official remediation level or patch link is provided beyond this version information, confirm with the vendor advisory for the latest patch status. Until upgraded, avoid using untrusted input for the base_url parameter or restrict network access to trusted hosts to reduce exposure.
CVE-2026-67425: CWE-201: Insertion of Sensitive Information Into Sent Data in flytohub flyto-core
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 v3.1
Score 8.6high
Affected software
pkg:github/flytohub/flyto-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Flyto-core versions before 2.26.6 contain a vulnerability where the llm.chat module reads sensitive environment variables containing provider API keys and includes them in the Authorization: Bearer header when making requests to a base_url controlled by the caller. This behavior allows an attacker to receive these sensitive keys if they can direct requests to a public host that circumvents the server-side request forgery (SSRF) guard. The vulnerability is classified under CWE-201 (Insertion of Sensitive Information Into Sent Data) and CWE-522 (Insufficiently Protected Credentials). The issue is resolved in flyto-core version 2.26.6.
Potential Impact
An attacker who can control the base_url parameter and direct requests to a public host that bypasses SSRF protections can obtain sensitive API keys (e.g., OPENAI_API_KEY, ANTHROPIC_API_KEY) from the environment. This exposure can lead to unauthorized use of these keys, potentially resulting in data breaches or abuse of the associated AI services. The vulnerability does not affect integrity or availability directly but results in a high confidentiality impact.
Mitigation Recommendations
This vulnerability is fixed in flyto-core version 2.26.6. Users should upgrade to version 2.26.6 or later to remediate this issue. Since no official remediation level or patch link is provided beyond this version information, confirm with the vendor advisory for the latest patch status. Until upgraded, avoid using untrusted input for the base_url parameter or restrict network access to trusted hosts to reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-29T15:02:20.413Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6a4bfc9c2644c7f8e93ec5
Added to database: 07/29/2026, 18:52:44 UTC
Last enriched: 07/29/2026, 19:09:46 UTC
Last updated: 07/29/2026, 19:23:01 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.