CVE-2026-67427
Workflow resolver expands env vars allowing secret exfiltration via workflow inputs.
Is CVE-2026-67427 being exploited?
Not confirmed. CVE-2026-67427 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-67427?
CVE-2026-67427 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67427?
Yes. A fix has been recorded for CVE-2026-67427. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67427 affect?
CVE-2026-67427 affects Flyto2 Core < 2.26.6, AI-agent/automation workflows using Flyto2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67427?
Upgrade Flyto2 Core to 2.26.6; audit workflows and restrict env variable exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Workflow parameters can access host environment variables and bypass capability policies to exfiltrate secrets via allowed modules.
Immediate action required
- affected< 2.26.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.