CVE-2026-35582
HighCVSS 8.8Exploitation Probability (EPSS)
Elevated risk58th percentile - higher than 58% of all known CVEs
Summary
Emissary versions 8.42.0 and below contain an OS command injection vulnerability in Executrix.getCommand() because temporary file paths are interpolated into a /bin/sh -c shell command string without escaping. The IN_FILE_ENDING and OUT_FILE_ENDING configuration keys flow directly into these paths, allowing a place author who can edit a .cfg file to inject shell metacharacters and execute commands in the JVM process's security context.
Risk Assessment
A user with place configuration privileges can execute arbitrary OS commands in the JVM process context, potentially leading to server compromise. The vulnerability requires no administrative privileges or network access.
Recommendation
Update Emissary to version 8.43.0, which fixes the vulnerability. Until updated, restrict the ability to modify .cfg files to trusted users.
Other vulnerabilities in Emissary
See all- CVE-2026-35583Medium
Emissary before 8.39.0 validates configuration names in the /api/configuration/{name} endpoint using a blacklist checking for \, /, .., and trailing ... This can be bypassed using URL-encoded variants, double-encoding, or Unicode normalization to achieve path traversal and read configuration files outside the intended directory. Fixed in 8.39.0.
- CVE-2026-35571Medium
Emissary prior to 8.39.0 interpolated configuration-controlled link values directly into href attributes in Mustache navigation templates without URL scheme validation. An administrator able to modify the navItems configuration could inject javascript: URIs, enabling stored XSS against other authenticated users viewing the Emissary web interface.
Original NVD description (English source)
Emissary is a P2P based data-driven workflow engine. In versions 8.42.0 and below, Executrix.getCommand() is vulnerable to OS command injection because it interpolates temporary file paths into a /bin/sh -c shell command string without any escaping or input validation. The IN_FILE_ENDING and OUT_FILE_ENDING configuration keys flow directly into these paths, allowing a place author who can write or modify a .cfg file to inject arbitrary shell metacharacters that execute OS commands in the JVM process's security context. The framework already sanitizes placeName via an allowlist before embedding it in the same shell string, but applies no equivalent sanitization to file ending values. No runtime privileges beyond place configuration authorship, and no API or network access, are required to exploit this vulnerability. This is a framework-level defect with no safe mitigation available to downstream implementors, as Executrix provides neither escaping nor documented preconditions against metacharacters in file ending inputs. This issue has been fixed in version 8.43.0.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS