Path Traversal in flyto-core (CVE-2026-67429)
Summary
Path traversal in flyto-core (CVE-2026-67429). Data can be tampered with by attackers. Exploitable via image.download. 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.6, image.download and related file-writing modules use caller-controlled output_dir instead of validate_path_with_env_config and its FLYTO_SANDBOX_DIR confinement, allowing attacker-controlled response bytes to be written to arbitrary filesystem paths the process can access. This issue is fixed in version 2.26.6.
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-67429 has been found in flyto-core.
Attackers can target a specific entry point like image.download over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 10.0/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-67429" on the vendor's site.
CVE-2026-67429 (flyto-core) — CWE-22 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: image.download / validate_path_with_env_config / FLYTO_SANDBOX_DIR / output_dir
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.
Path traversal (CWE-22) exists in flyto-core. Attackers reach the vulnerable code path via image.download without authentication.
Check the vendor advisory for the affected versions of flyto-core. Attack surface: image.download / validate_path_with_env_config / FLYTO_SANDBOX_DIR / output_dir.
Severity: Critical (CVSS 10.0/10). Data can be tampered with by attackers.
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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flyto-core to 2.26.7ステージング環境で 2.26.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
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