Security readout for executives and security teams
Plain-English summary
Yamcs versions before 5.12.7 can let algorithm editing become server command execution. In insecure default setups, this may be reachable without authentication because the guest user can be superuser when no security.yaml is present. Successful abuse could fully compromise the Yamcs process and the host context it runs in.
Executive priority
Treat this as urgent for any operational Yamcs deployment. The business risk is full server compromise of mission control infrastructure, with confidentiality, integrity, and availability impact. Upgrade and privilege review should be scheduled immediately for exposed or default-configured systems.
Technical view
The advisory describes Nashorn JavaScript algorithm evaluation without a ClassFilter in ScriptAlgorithmExecutorFactory. An actor able to update mission database algorithms through MdbOverrideApi.updateAlgorithm can cause arbitrary Java class access and OS command execution as the Yamcs process. The issue is fixed in 5.12.7 and 5.13.0, which disable algorithm editing by default.
Likely exposure
Highest exposure is Yamcs before 5.12.7, especially deployments without security.yaml or with broad ChangeMissionDatabase privileges. Systems exposing Yamcs administrative or API functionality to untrusted networks should be prioritized. The source bundle names yamcs/yamcs only; no other products are evidenced.
Exploitation context
The CVSS vector is network, low complexity, no user interaction, and potentially no privileges in the default no-security configuration. The bundle does not show CISA KEV listing or another cited source confirming active exploitation, so active exploitation should not be stated.
Researcher notes
Key research areas are privilege boundaries around ChangeMissionDatabase, presence of security.yaml, and whether algorithm editing remains enabled. Evidence is source-limited to the advisory, CVE data, commits, and release pages; no active exploitation evidence is provided.
Mitigation direction
- Upgrade Yamcs to 5.12.7 or 5.13.0.
- Review Yamcs vendor guidance before enabling algorithm editing again.
- Configure security.yaml; avoid the default guest superuser exposure.
- Remove ChangeMissionDatabase from users who do not require it.
- Limit Yamcs administrative/API access to trusted operators and networks.
Validation and detection
- Inventory Yamcs versions and flag any instance before 5.12.7.
- Check whether security.yaml exists and is actively enforced.
- Review users and roles for ChangeMissionDatabase privilege assignments.
- Confirm algorithm editing is disabled after upgrade.
- Verify remediation against the Yamcs advisory and release notes.
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-470: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-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 lookupCWE-95: 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-46562 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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-vmwp-vh32-rj75CVE 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.
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.