AAK-MCP-FLYTO-CVE-2026-67425-001: Flyto2 Core forwards provider API keys to a caller-controlled base_url, and its HTTP MCP route runs modules unauthenticated (below 2.26.6)
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
Flyto2CoreProviderKeyExfil
What it detects
Flyto2 Core (flyto-core), an MCP-native execution kernel for AI-agent workflows, before 2.26.6 has llm.chat read provider credentials such as OPENAI_API_KEY and ANTHROPIC_API_KEY from the environment and send them in the Authorization: Bearer header to a caller-controlled base_url. An actor who can steer base_url to a public host that clears the SSRF guard receives the operator's provider key (CVE-2026-67425, CVSS 8.6). Fixed in 2.26.6; treat < 2.26.6 (and unpinned) as exposed. The env-var-key exfil-to-caller-controlled-endpoint class here is adjacent to the config-side env-secret exfil surface AAK-MCP-ENV-PLACEHOLDER-EXFIL-001 covers. CVE-2026-55786 (CVSS 8.4) sits under the same floor: from 2.26.2 to 2.26.3 the HTTP MCP route (POST /mcp) takes tools/call requests without the require_auth dependency the REST execution routes use, so an unauthenticated caller can run execute_module with sandbox.execute_shell and a command of its choosing. Fixed in 2.26.4.
How to fix
Upgrade flyto-core to >= 2.26.6 and pin it. Restrict llm.chat base_url to an allow-list of trusted provider hosts, and never forward environment-sourced provider keys to a caller-supplied endpoint. Until the upgrade, do not expose the HTTP API, whose /mcp route runs modules without authentication from 2.26.2 to 2.26.3, beyond localhost.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-FLYTO-CVE-2026-67425-001
Limitations
Reads flyto-core in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, taking the lowest version a range allows and reporting a reference that states no version. The dependency is not read when it is declared in a sub-directory manifest (services/api/pyproject.toml) or in a lockfile format the reader does not parse (pdm.lock). A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-67425, CVE-2026-55786
- OWASP MCP Top 10: MCP01:2025 (Token Mismanagement & Secret Exposure), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution), MCP07:2025 (Insufficient Authentication & Authorization)
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution (RCE))
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
- CSA AI Controls Matrix (AICM): DSP-17, STA-08, IVS-04
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-FLYTO-CVE-2026-67425-001.md: the page then shows that text, with the registry reference appended under it.