CVE-2026-35580: Emissary has GitHub Actions Shell Injection via Workflow Inputs

CVE-2026-35580 · Severity: critical · CVSS 9.1 · Published 2026-04-07

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.

Technologies: gov.nsa.emissary:emissary (Maven), Nsa Emissary. Vendors: Maven, Nsa.

Quick answers

Is CVE-2026-35580 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-35580 being exploited in the wild.
How severe is CVE-2026-35580?
Critical severity, with a CVSS score of 9.1, published 7 April 2026.
Which products and versions are affected?
gov.nsa.emissary:emissary (Maven) ECOSYSTEM:introduced=0,fixed=8.39.0.
Is there a fix for CVE-2026-35580?
Yes. gov.nsa.emissary:emissary (Maven): upgrade to 8.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-35580?
Check whether you run gov.nsa.emissary:emissary (Maven) or Nsa Emissary at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • gov.nsa.emissary:emissary (Maven): upgrade to 8.39.0 or later
    # set gov.nsa.emissary:emissary to 8.39.0 in your pom.xml or build.gradle

Affected products

  • gov.nsa.emissary:emissary (Maven) ECOSYSTEM:introduced=0,fixed=8.39.0
  • Nsa Emissary

Identifiers

  • CVE-2026-35580
  • GHSA-3g6g-gq4r-xjm9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.