Local command execution via unsafe file endings
Published Apr 18, 2026 · Updated Apr 18, 2026
OS command injection in Emissary 8.42.0 and earlier allows local users to execute commands through crafted place configuration. Executrix.getCommand() substitutes temporary paths derived from unvalidated IN_FILE_ENDING and OUT_FILE_ENDING values into a /bin/sh -c command string. Place configuration authorship is required, and injected shell metacharacters run in the JVM process's security context when the place processes a payload.
Summary
What happened
OS command injection in Emissary 8.42.0 and earlier allows local users to execute commands through crafted place configuration. Executrix.getCommand() substitutes temporary paths derived from unvalidated IN_FILE_ENDING and OUT_FILE_ENDING values into a /bin/sh -c command string. Place configuration authorship is required, and injected shell metacharacters run in the JVM process's security context when the place processes a payload.
The record
- CVE
- CVE-2026-35582
- Published
- Apr 18, 2026
- Updated
- Apr 18, 2026
- Vendor
- National Security Agency
- Product
- Emissary
- Classifications
- CWE-78, CWE-116, T1059.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2026CVE publishedPublication date reported by the CVE source.
- Apr 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.43.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA configuration payload demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo