CVE-2026-67425: high-severity vulnerability in flytohub flyto-core
Flyto2 Core: LLM/API keys leak to an attacker-controlled base_url
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.6epss 0.4%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Affected products
flytohub · flyto-coreRelated CVEs — flytohub flyto-core
In the same product, most dangerous first.
CVE-2026-67429CRITICALFlyto2 Core: Arbitrary file write via image.download (and other file-writing modules)EPSS 0.6%CVE-2026-67427HIGHFlyto2 Core: ${env.VAR} interpolation reads any env secret despite env.get being denylistedEPSS 0.4%CVE-2026-73530MEDIUMFlyto2 Core < 2.28.0 SSRF Guard Bypass via is_private_ip()EPSS 0.4%CVE-2026-55786HIGHFlyto2 Core: Unauthenticated Command Execution via HTTP MCP `execute_module`EPSS 0.4%CVE-2026-67428HIGHFlyto2 Core: Multiple HTTP-family modules fetch client-controlled URLs without the SSRF guard their siblings apply (SSRF to internal/metadata)EPSS 0.4%CVE-2026-67426CRITICALFlyto2 Core: Unauthenticated flyto-verification /run: callback_url SSRF and internal runner-secret exfiltrationEPSS 0.4%