Security readout for executives and security teams
Plain-English summary
Yamcs before 5.12.7 allowed a highly privileged authenticated user to turn editable mission database algorithms into server-side Java execution. In practical terms, a trusted Yamcs user with the right privilege could potentially run code on the host. Fixed versions disable algorithm editing by default.
Executive priority
Treat as urgent for any operational Yamcs environment. The required privilege narrows exposure, but successful abuse could compromise the mission control host. Prioritize upgrades and privilege review, especially where Yamcs is reachable by multiple operators or integrated service accounts.
Technical view
The flaw is CWE-94 code injection in org.yamcs.algorithms.JavaExprAlgorithmExecutionFactory. User-controlled algorithm text was dynamically compiled through Janino without a secure sandbox. An authenticated user with ChangeMissionDatabase could override algorithm text through the mission database REST API, leading to host-level remote code execution.
Likely exposure
Exposure is limited to Yamcs deployments before 5.12.7 where authenticated users or service accounts have ChangeMissionDatabase privilege. The source bundle identifies yamcs/yamcs versions below 5.12.7 as affected. No other products or CPEs are provided.
Exploitation context
The bundle does not show KEV listing or active exploitation evidence. Exploitation requires valid authentication and the high-impact ChangeMissionDatabase privilege, but CVSS indicates network reachability, low attack complexity, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Researcher notes
Evidence supports a Janino-based server-side code injection path in JavaExprAlgorithmExecutionFactory, fixed by disabling algorithm editing by default in 5.12.7 and 5.13.0. The bundle does not provide proof of exploitation, detailed indicators, or affected downstream distributions.
Mitigation direction
- Upgrade Yamcs to 5.12.7 or 5.13.0.
- Confirm algorithm editing is disabled by default after upgrade.
- Review and restrict ChangeMissionDatabase privilege assignments.
- Check vendor advisory and release notes for environment-specific guidance.
- Review logs for recent mission database algorithm text changes.
Validation and detection
- Inventory Yamcs instances and record exact versions.
- Identify users or service accounts with ChangeMissionDatabase privilege.
- Review mission database API activity for algorithm overrides.
- Verify upgraded systems reject unauthorized algorithm editing.
- Confirm change management captured any algorithm edits before patching.
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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-44632 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-524g-x36v-9wm6CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/yamcs/yamcs/commit/3c550348f866af4675d2ba4a51d8d12b7c7c6011CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/commit/4ff8fda642ea8c3309a4d3f379aa77b763148992CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.7CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.0CVE 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.