CVE-2026-67426: Flyto2 Core: Unauthenticated flyto-verification /run: callback_url SSRF and internal runner-secret exfiltration
(updated )
The standalone flyto-verification service exposes POST /run with no authentication, on all interfaces (0.0.0.0:8344 per the shipped Dockerfile). The request body’s callback_url is used verbatim for an outbound POST that unconditionally attaches X-Internal-Key: $FLYTO_RUNNER_SECRET. The callback_url bypasses the service’s target_allowed allowlist (which only inspects params.target_url) and is never passed through any SSRF guard. This yields (a) unauthenticated SSRF to internal/metadata endpoints with an attacker-controlled JSON body, and (b) exfiltration of the internal runner secret to an attacker-controlled host — allowing forged authenticated callbacks to the real engine.
References
- github.com/advisories/GHSA-jx74-cqjv-2c67
- github.com/flytohub/flyto-core/commit/0a0a528520ec18f5a21f1ddf858a71cc1edfb6e9
- github.com/flytohub/flyto-core/releases/tag/v2.26.7
- github.com/flytohub/flyto-core/security/advisories/GHSA-jx74-cqjv-2c67
- github.com/pypa/advisory-database/tree/main/vulns/flyto-core/PYSEC-2026-3571.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-67426
Code Behaviors & Features
Detect and mitigate CVE-2026-67426 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →