# CVE-2026-55511: Yamcs authenticated RCE via StreamSQL column-name injection

Source: https://junglewise.ai/threats/cve-2026-55511-yamcs-authenticated-rce-via-streamsql-column-name-injection  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-28. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-55511 · Severity: critical · CVSS 9.1 · Published 2026-08-28

Yamcs is a space mission control system that processes telemetry data using a query language called StreamSQL. The system dynamically compiles StreamSQL queries to Java bytecode but fails to sanitize column names before inserting them into the generated code. An authenticated operator with archive-management privileges can craft a malicious column name containing Java code, which executes with the privileges of the Yamcs server process, allowing complete compromise of mission data, telemetry tampering, and lateral movement into the host environment.

Technologies: [org.yamcs:yamcs-core (Maven)](https://junglewise.ai/threats/technologies/org-yamcs-yamcs-core), [Yamcs](https://junglewise.ai/threats/technologies/yamcs). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven), [Yamcs](https://junglewise.ai/threats/vendors/yamcs).

## Quick answers

**Is CVE-2026-55511 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-55511 being exploited in the wild.

**How severe is CVE-2026-55511?** Critical severity, with a CVSS score of 9.1, published 28 August 2026.

**Which products and versions are affected?** org.yamcs:yamcs-core (Maven) ECOSYSTEM:introduced=5.13.0,fixed=5.13.2; Yamcs >=5.13.0, <=5.13.1 and <=5.12.7.

**Is there a fix for CVE-2026-55511?** Yes. org.yamcs:yamcs-core (Maven): upgrade to 5.13.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-55511 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-55511?** Check whether you run org.yamcs:yamcs-core (Maven) or Yamcs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.yamcs:yamcs-core (Maven): upgrade to 5.13.2 or later

  ```sh
  # set org.yamcs:yamcs-core to 5.13.2 in your pom.xml or build.gradle
  ```


## Technical details

The vulnerability is a code-injection flaw in the StreamSQL expression compiler (org.yamcs.yarch.streamsql). When compiling aggregate functions like sum(...), Yamcs interpolates column names unescaped into generated Java source code. The sanitizeName() function only removes forward-slashes and hyphens, leaving characters like semicolons, parentheses, and braces intact. This allows an attacker to break out of the identifier context and inject arbitrary Java statements. Unlike the bare-expression compiler (which has an accidental mitigation), the aggregate compiler lacks a return statement that would cause injected code to be flagged as unreachable, making arbitrary code execution possible. An authenticated attacker with SystemPrivilege.ControlArchiving can exploit this via POST /api/archive/{instance}:executeSql by creating a table with a malicious column name (e.g., containing java.io.File().mkdirs() or other JDK APIs) and executing a SELECT sum(...) query that triggers compilation and execution of the injected code. Patches are available in versions 5.13.2 and 5.12.8.

## Affected products

- Yamcs yamcs-core >=5.13.0, <=5.13.1 and <=5.12.7

## Identifiers

- CVE-2026-55511
- GHSA-3g44-3m7x-cgg2

## Timeline

- 2026-07-14: disclosed: Published in GitHub Advisory Database
- 2026-08-28: advisory: Advisory updated with additional technical details
- 2026-08-28: patched: Patches released in versions 5.13.2 and 5.12.8

## References

- [https://api.github.com/users/Yanchon918s](https://api.github.com/users/Yanchon918s)
- [https://github.com/Yanchon918s](https://github.com/Yanchon918s)
- [https://api.github.com/users/Yanchon918s/gists%7B/gist_id%7D](https://api.github.com/users/Yanchon918s/gists%7B/gist_id%7D)
- [https://api.github.com/users/Yanchon918s/repos](https://api.github.com/users/Yanchon918s/repos)
- [https://avatars.githubusercontent.com/u/124195190?v=4](https://avatars.githubusercontent.com/u/124195190?v=4)
- [https://api.github.com/users/Yanchon918s/events%7B/privacy%7D](https://api.github.com/users/Yanchon918s/events%7B/privacy%7D)

## Related threats

- [Yamcs DOM XSS in Extension Routing](https://junglewise.ai/threats/cve-2026-55566-yamcs-dom-xss-in-extension-routing)
- [Yamcs remote code execution via unescaped StreamSQL LIKE pattern](https://junglewise.ai/threats/cve-2026-55565-yamcs-remote-code-execution-via-unescaped-streamsql-like-pattern)
- [Yamcs remote code execution via YAML injection in instance template](https://junglewise.ai/threats/cve-2026-55559-yamcs-remote-code-execution-via-yaml-injection-in-instance)
- [Yamcs unauthenticated directory traversal](https://junglewise.ai/threats/cve-2026-55552-yamcs-unauthenticated-directory-traversal)
- [Yamcs reflected XSS in authorize endpoint](https://junglewise.ai/threats/cve-2026-55549-yamcs-reflected-xss-in-authorize-endpoint)