CVE-2026-67429

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Arbitrary file write via image.download (and other file-writing modules) · Advisory · flytohub/flyto-core · GitHub

https://github.com/flytohub/flyto-core/security/advisories/GHSA-2956-977x-2w3r
github_release Patch Available

v2.26.6 — Security release

Patch available: flytohub/flyto-core v2.26.6

https://github.com/flytohub/flyto-core/releases/tag/v2.26.6
github_commit Patch Available

commit d5f89d71303e (flytohub/flyto-core)

Patch available: flytohub/flyto-core v2.26.6 (contains commit d5f89d71303e)

https://github.com/flytohub/flyto-core/commit/d5f89d71303e3c1e6418d347c5c55fcd173cc8cc

Vendor Advisories for CVE-2026-67429(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
flyto-core1.0.0 ... 2.9.0 (216 versions)2.26.7—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 15:11 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 17:53 UTCEG score recompute
  4. 2026-08-24 12:04 UTCEG score recompute
  5. 2026-08-23 01:53 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 00:26 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 03:10 UTCEG score recompute
  10. 2026-08-20 22:56 UTCEPSS rescore
  11. 2026-08-19 20:35 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 18:34 UTCEG score recompute
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 14:34 UTCEG score recompute
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 17:23 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 04:39 UTCEG score recompute
  20. 2026-08-15 03:15 UTCEG score recompute
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 01:49 UTCEG score recompute
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 15:54 UTCEG score recompute
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 29 more
  1. 2026-08-11 14:23 UTCEG score recompute
  2. 2026-08-11 01:40 UTCEG score recompute
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-09 15:46 UTCEG score recompute
  5. 2026-08-09 13:47 UTCEPSS rescore
  6. 2026-08-08 18:34 UTCEG score recompute
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-07 17:09 UTCEG score recompute
  9. 2026-08-06 15:44 UTCEG score recompute
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 22:46 UTCEG score recompute
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-04 16:46 UTCEG score recompute
  15. 2026-08-04 15:10 UTCEPSS rescore
  16. 2026-08-04 12:31 UTCEG score recompute
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 14:13 UTCEG score recompute
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-02 04:16 UTCEG score recompute
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 07:01 UTCEG score recompute
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-30 16:44 UTCEG score recompute
  25. 2026-07-30 16:28 UTCEPSS rescore
  26. 2026-07-30 13:22 UTCEG score recompute
  27. 2026-07-29 19:32 UTCEG score recompute
  28. 2026-07-29 18:53 UTCEG score recompute
  29. 2026-07-29 18:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67429?
CVE-2026-67429 is a critical vulnerability published on July 29, 2026. 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 outputdir instead of validatepathwithenvconfig and its FLYTOSANDBOX_DIR confinement, allowing attacker-controlled response bytes to be…
When was CVE-2026-67429 disclosed?
CVE-2026-67429 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67429 actively exploited?
CVE-2026-67429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.2% of all scored CVEs.
What is the CVSS score of CVE-2026-67429?
CVE-2026-67429 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-67429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67429, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67429

Explore →

Is Your Infrastructure Affected by CVE-2026-67429?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs