On this page

Atomicorp WAF Research Note: CVE-2026-55559

Yamcs: Remote Code Execution via instance-template argument YAML injection (createInstance)

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-55559
  • Name: Yamcs: Remote Code Execution via instance-template argument YAML injection (createInstance)
  • Severity: Critical
  • CVSS: 9.8 (v3.1) (Critical)
  • CVSS version: 3.1
  • CVSS source: GitHub_M CNA
  • CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    • Attack vector: Network
    • Attack complexity: Low
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: High
    • Integrity impact: High
    • Availability impact: High
  • CWE: CWE-94 — Improper Control of Generation of Code (‘Code Injection’), CWE-470 — Use of Externally-Controlled Input to Select Classes or Code (‘Unsafe Reflection’), CWE-1336 — Improper Neutralization of Special Elements Used in a Template Engine
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-138 , CAPEC-242 , CAPEC-35 , CAPEC-77
  • Vendor: yamcs
  • Vulnerable product: yamcs
  • CVE published: 2026-08-28
  • CVE last modified: 2026-09-08
  • EPSS: 0.0055; 44.4th percentile (FIRST )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655
  • Matching rules: 7; rules with blocking actions: 7
  • Would-block Rule IDs: 344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655
  • Request surfaces inspected: JSON request data, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data

Vulnerability Description

Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs inserts templateArgs from POST /api/instances and PATCH /api/instances/{instance} into YAML through VarStatement.append in yamcs-core/src/main/java/org/yamcs/templating/VarStatement.java without YAML-context escaping. The rendered configuration is parsed by YamcsServer.createInstance and loaded by YamcsServerInstance, allowing an attacker to inject a services entry for org.yamcs.ProcessRunner. Deployments without security.yaml expose the operation through the guest superuser, while secured deployments require SystemPrivilege.CreateInstances. Successful exploitation executes commands as the Yamcs service account. This issue is fixed in versions 5.12.8 and 5.13.2.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (344360 , 344361 , 344363 , 344364 , 344366 , 344370 , 393655 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: yamcs version < 5.12.8.
    • Affected versions: yamcs version >= 5.13.0, < 5.13.2.
    • No specific CNA/vendor solution or workaround is included in the current CVE Record . Review the vendor’s security advisories and supported-release guidance before making changes.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, rce, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .