Yamcs-Core ( < 5.12.7 ) — CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/yamcs-core---5.12.7-/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 27 May 2026 00:07:37 +0000Yamcs Server-Side Code Injection via Janino Expression Enginehttps://feed.craftedsignal.io/briefs/2026-05-yamcs-rce/Wed, 27 May 2026 00:07:37 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-05-yamcs-rce/A server-side code injection vulnerability exists in Yamcs algorithm evaluation engine, allowing an authenticated user with `ChangeMissionDatabase` privilege to achieve Remote Code Execution (RCE) by injecting a malicious Java payload via the Janino compiler.A server-side code injection vulnerability has been identified in Yamcs, specifically affecting the org.yamcs.algorithms.JavaExprAlgorithmExecutionFactory component. This flaw allows an authenticated user with the ChangeMissionDatabase privilege to inject arbitrary Java code into the algorithm evaluation engine. The application dynamically compiles and evaluates this user-controlled algorithm text using the Janino compiler, but lacks a secure sandbox to prevent malicious code execution. Exploitation leads to Remote Code Execution (RCE) on the underlying host operating system. Discovered and reported by Pablo Picurelli Ortiz, this vulnerability is present in Yamcs versions prior to 5.12.7.

Attack Chain

  1. An attacker gains valid credentials to a Yamcs instance with an active processor (e.g., instance=myproject, processor=realtime).
  2. The attacker authenticates to the Yamcs REST API using the acquired credentials, ensuring they possess the SystemPrivilege.ChangeMissionDatabase privilege.
  3. The attacker crafts a malicious Java payload designed to execute arbitrary OS commands. This payload often utilizes java.lang.Runtime.getRuntime().exec() to initiate a reverse shell or establish an external webhook connection.
  4. The attacker sends an authenticated HTTP PATCH request to the MDB override endpoint, targeting an existing algorithm (e.g., copySunsensor). The request body contains the malicious Java code within the text field of the algorithm definition.
  5. The Yamcs server receives the PATCH request and updates the targeted algorithm’s text with the attacker-supplied Java code.
  6. The attacker triggers the evaluation of the modified algorithm. This can be achieved by sending telemetry data that the algorithm depends on, simulating real-world sensor readings.
  7. The Yamcs server employs the Janino SimpleCompiler to dynamically compile the injected Java text into a Java class. Due to the absence of a restrictive ClassLoader, the compilation process proceeds without any security constraints.
  8. The compiled malicious Java code is executed by the Yamcs server, resulting in arbitrary command execution on the host operating system. This allows the attacker to perform actions such as data exfiltration or lateral movement.

Impact

Successful exploitation of this vulnerability grants an attacker with application-level configuration privileges full control over the Yamcs server’s underlying operating system. This can lead to arbitrary command execution, sensitive data exfiltration, and the potential for lateral movement within the network where the Yamcs server is hosted. The impact is severe, potentially compromising the entire system and its data.

Recommendation

  • Upgrade Yamcs to version 5.12.7 or later to patch CVE-2026-44632.
  • Implement strict access controls to limit the number of users with the ChangeMissionDatabase privilege.
  • Deploy the Sigma rules provided in this brief to detect attempts to inject malicious Java code into Yamcs algorithms.
  • Monitor network traffic for connections to the webhook URL provided in the IOC table.
]]>criticalthreatrcecode-injectionyamcs