Vulnerability in flyto-core (CVE-2026-67426)
Summary
Vulnerability in flyto-core (CVE-2026-67426). Confidential information can be exposed externally. Exploitable via POST /run. Mitigation: upgrade to 2.26.7 or later.
Original description
The description as published by the source.
Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, the standalone flyto-verification service in src/core/verification_service.py exposes unauthenticated POST /run on 0.0.0.0:8344 and uses client-supplied callback_url for an outbound POST with X-Internal-Key: $FLYTO_RUNNER_SECRET while bypassing target_allowed, allowing unauthenticated SSRF and runner secret exfiltration. This issue is fixed in version 2.26.7.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-67426 has been found in flyto-core.
Attackers can target a specific entry point like POST /run over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: upgrade flyto-core to 2.26.7 or later.
If unsure, ask your IT team or search "flyto-core CVE-2026-67426" on the vendor's site.
CVE-2026-67426 (flyto-core) — CWE-306 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /run / callback_url / target_allowed / params.target_url
Patched: 2.26.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in flyto-core. Attackers reach the vulnerable code path via POST /run without authentication.
Check the vendor advisory for the affected versions of flyto-core. Attack surface: POST /run / callback_url / target_allowed / params.target_url.
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally.
Update to 2.26.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /run requests with malformed payloads or SQL meta-characters. Run grep -r 'flyto-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'flyto-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flyto-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /run' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /runへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade flyto-core to 2.26.7ステージング環境で 2.26.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /run on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web github.com
- web github.com