CVE-2026-35580
Shell-injection in Emissary workflows allows repo write attackers to run commands.
Is CVE-2026-35580 being exploited?
Not confirmed. CVE-2026-35580 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.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-35580?
CVE-2026-35580 is rated Critical with a CVSS score of 9.1. 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-35580?
Yes. A fix has been recorded for CVE-2026-35580. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-35580 affect?
CVE-2026-35580 affects Emissary data-driven workflow engine (<8.39.0), GitHub Actions workflow files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-35580?
Upgrade to 8.39.0+; audit workflow inputs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Code execution via workflow_dispatch; repository poisoning and downstream supply chain risk.
Patch when possible
- affected< 8.39.0
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.