Security readout for executives and security teams
Plain-English summary
A highly privileged Yamcs user can abuse archive SQL processing to run arbitrary Java inside the server. A successful compromise could expose mission data and credentials, alter telemetry, or disrupt operations. The flaw is critical despite requiring authentication because the resulting code runs with the Yamcs process's authority.
Executive priority
Treat this as an urgent upgrade for affected mission-control environments. Prioritize internet-accessible or broadly reachable systems and those with numerous privileged accounts. Because compromise could affect confidentiality, telemetry integrity, and availability, pair remediation with focused review of privileged access and recent archive API activity.
Technical view
Yamcs improperly interpolates a double-quoted StreamSQL column name into generated Java for aggregate processing. A sum expression can carry the injected source through compilation, where Janino compiles it in the Yamcs server process. The vulnerable network-accessible executeSql API requires SystemPrivilege.ControlArchiving. This is CWE-94 with CVSS 3.1 score 9.1.
Likely exposure
Exposure exists where Yamcs versions below 5.12.8, or versions 5.13.0 through 5.13.1, are deployed and accounts hold SystemPrivilege.ControlArchiving. Risk increases when the archive API is reachable from less-trusted networks or privileged credentials are compromised.
Exploitation context
The supplied sources establish authenticated remote code execution requiring a high-privilege account and no user interaction. They do not establish active exploitation, and the CVE is not identified as being in KEV. Public technical details may still increase attacker awareness.
Researcher notes
The vulnerable path involves Expression.fillCode_InputDefVars, Expression.sanitizeName, aggregate compilation, SumExpression, and Janino SimpleCompiler.cook. The root issue is generated-code injection through an inadequately handled identifier. The source bundle identifies two corrective commits, but does not provide evidence of exploitation in the wild.
Mitigation direction
- Upgrade the 5.12 branch to Yamcs 5.12.8 or later.
- Upgrade the 5.13 branch to Yamcs 5.13.2 or later.
- Review and minimize assignments of SystemPrivilege.ControlArchiving.
- Restrict archive API access to trusted administrative networks while upgrades are pending.
- Rotate potentially exposed credentials if investigation indicates server compromise.
Validation and detection
- Inventory every Yamcs deployment and confirm its exact running version.
- Identify all users and service accounts holding SystemPrivilege.ControlArchiving.
- Verify upgraded systems report version 5.12.8, 5.13.2, or a later applicable release.
- Review executeSql access records for unexpected privileged users, sources, or queries.
- Investigate process, telemetry, and credential activity for signs of unauthorized changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-55511 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/yamcs/yamcs/security/advisories/GHSA-3g44-3m7x-cgg2CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/yamcs/yamcs/commit/8c1070b12c0a6c003903325cb2a1013347e2dbdeCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/commit/b65a3d78178ba99a58b753feda6ecc3b5a694f13CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.