Emissary has an OS Command Injection via Unvalidated IN_FILE_ENDING / OUT_FILE_ENDING in Executrix

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2026-35582: 0.86% estimated exploitation activity in the next 30 days; percentile 58.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Executrix.getCommand() constructs shell commands by substituting temporary file paths directly into a /bin/sh -c string with no escaping. The INFILEENDING and OUTFILEENDING configuration keys flow into those paths unmodified. A place author who sets either key to a shell metacharacter sequence achieves arbitrary OS command execution in the JVM's security context when the place processes any payload. No runtime privileges beyond place configuration authorship are required, and no API or network access is needed. This is a framework-level defect — Executrix provides no escaping mechanism and no validation on file ending values. Downstream implementors have no safe way to use the API as designed. --- Root Cause Step 1 — INFILEENDING flows into temp path construction without validation TempFileNames.java:32-36 inFileEnding is concatenated directly onto a numeric base to produce inputFilename. No character class, no regex, no escaping. Step 2 — The injected path is substituted…

Published by the source

13 Apr 2026, 16:38 UTC

Last modified by the source

24 Apr 2026, 20:52 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3p24-9x7v-7789

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35582

Advisory: Emissary has an OS Command Injection via Unvalidated IN_FILE_ENDING / OUT_FILE_ENDING in Executrix
IDs: CVE-2026-35582, GHSA-3p24-9x7v-7789
Record: https://patchnext.com/advisories/cve-2026-35582 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gov.nsa.emissary:emissary 8.43.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven gov.nsa.emissary:emissary: affected <= 8.42.0; fixed in 8.43.0

## Suggested inspection (read-only)
- Maven gov.nsa.emissary:emissary: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gov.nsa.emissary:emissary.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3p24-9x7v-7789 (GitHub-reviewed advisory GHSA-3p24-9x7v-7789 lists affected ranges: Maven gov.nsa.emissary:emissary >=0 <=8.42.0)

Commands are suggestions: review each one before running it.