CVE-2026-67428

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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
Elevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: Elevated riskExposed: 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.7, HTTP-emitting modules including src/core/modules/third_party/developer/http/requests.py, core.api.http_get, core.api.http_post, graphql.query, graphql.mutation, monitor.http_check, communication.slack_send, notification.discord.send_message, notification.slack.send_message, notification.teams.send_message, ai.vision_analyze, verify.visual_diff, browser.proxy_rotate, and the agent and llm inline base_url branch fetch caller-controlled URLs without validate_url_with_env_config, allowing SSRF to internal or metadata endpoints. This issue is fixed in version 2.26.7.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
54(Track)
EG Risk 54/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
Severity85% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v2.26.7 — Security release (SSRF hardening)

Patch available: flytohub/flyto-core v2.26.7

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

commit 0a0a528520ec (flytohub/flyto-core)

Patch available: flytohub/flyto-core v2.26.7 (contains commit 0a0a528520ec)

https://github.com/flytohub/flyto-core/commit/0a0a528520ec18f5a21f1ddf858a71cc1edfb6e9
github Patch Available🟡 PoC Available

Multiple HTTP-family modules fetch client-controlled URLs without the SSRF guard their siblings apply (SSRF to internal/metadata) · Advisory · flytohub/flyto-core · GitHub

https://github.com/flytohub/flyto-core/security/advisories/GHSA-pgwh-4jj4-qm8v

Vendor Advisories for CVE-2026-67428(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(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 53× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 23:12 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 20:55 UTCEG score recompute
  5. 2026-08-26 15:35 UTCEG score recompute
  6. 2026-08-26 14:47 UTCEPSS rescore
  7. 2026-08-25 14:20 UTCEG score recompute
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 01:43 UTCEG score recompute
  10. 2026-08-24 13:09 UTCEG score recompute
  11. 2026-08-23 11:59 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 10:49 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 09:38 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-19 19:52 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 18:34 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-18 01:23 UTCEG score recompute
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 00:08 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 11:32 UTCEG score recompute
Show 35 more
  1. 2026-08-15 10:23 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 09:13 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 19:28 UTCEG score recompute
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-11 18:18 UTCEG score recompute
  8. 2026-08-11 05:42 UTCEG score recompute
  9. 2026-08-11 00:00 UTCEPSS rescore
  10. 2026-08-09 15:57 UTCEG score recompute
  11. 2026-08-09 13:47 UTCEPSS rescore
  12. 2026-08-09 03:23 UTCEG score recompute
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-08 02:13 UTCEG score recompute
  15. 2026-08-07 01:03 UTCEG score recompute
  16. 2026-08-06 13:47 UTCEPSS rescore
  17. 2026-08-05 23:54 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-04 22:44 UTCEG score recompute
  21. 2026-08-04 15:10 UTCEPSS rescore
  22. 2026-08-04 10:39 UTCEPSS rescore
  23. 2026-08-03 21:30 UTCEG score recompute
  24. 2026-08-03 10:36 UTCEPSS rescore
  25. 2026-08-02 07:46 UTCEG score recompute
  26. 2026-08-02 02:27 UTCEPSS rescore
  27. 2026-08-01 06:36 UTCEG score recompute
  28. 2026-08-01 04:16 UTCEPSS rescore
  29. 2026-07-30 16:44 UTCEG score recompute
  30. 2026-07-30 16:28 UTCEPSS rescore
  31. 2026-07-30 15:38 UTCEG score recompute
  32. 2026-07-30 15:00 UTCEG score recompute
  33. 2026-07-29 19:32 UTCEG score recompute
  34. 2026-07-29 18:53 UTCEG score recompute
  35. 2026-07-29 18:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67428?
CVE-2026-67428 is a high vulnerability published on July 29, 2026. Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, HTTP-emitting modules including src/core/modules/thirdparty/developer/http/requests.py, core.api.httpget, core.api.httppost, graphql.query, graphql.mutation, monitor.httpcheck, communication.slacksend,…
When was CVE-2026-67428 disclosed?
CVE-2026-67428 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-67428 actively exploited?
CVE-2026-67428 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 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-67428?
CVE-2026-67428 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-67428?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67428, 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-67428

Explore →

Is Your Infrastructure Affected by CVE-2026-67428?

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

Start Free Scan →Browse All CVEs