Remote code execution via template argument YAML injection
Published Aug 28, 2026 · Updated Aug 28, 2026
Code injection in Space Applications Services Yamcs before 5.12.8 and 5.13.0 through 5.13.1 allows remote attackers to execute commands. VarStatement.append inserts templateArgs into rendered YAML without context escaping, so the parser accepts an injected services entry for org.yamcs.ProcessRunner. The API is unauthenticated without security.yaml; otherwise CreateInstances privilege is required, and commands run as the Yamcs service account.
Summary
What happened
Code injection in Space Applications Services Yamcs before 5.12.8 and 5.13.0 through 5.13.1 allows remote attackers to execute commands. VarStatement.append inserts templateArgs into rendered YAML without context escaping, so the parser accepts an injected services entry for org.yamcs.ProcessRunner. The API is unauthenticated without security.yaml; otherwise CreateInstances privilege is required, and commands run as the Yamcs service account.
The record
- CVE
- CVE-2026-55559
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Space Applications Services
- Product
- Yamcs
- Classifications
- CWE-1336, CWE-94, CWE-470, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=< 5.12.8
- Affected versionversion=>= 5.13.0, < 5.13.2
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
- Instance-template YAML injection proof of conceptproof 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