Code Injection in org.yamcs:yamcs-core (CVE-2026-46621)
Summary
Code injection in org.yamcs:yamcs-core (CVE-2026-46621). Successful exploitation can lead to full system takeover. Exploitable via ChangeMissionDatabase. Mitigation: upgrade to 5.12.7 or later.
Original description
The description as published by the source.
Yamcs is a mission control framework. Prior to 5.12.7, the Yamcs script evaluation engine for Python algorithms dynamically compiled and evaluated user-controlled algorithm text using Jython through the JSR-223 ScriptEngine API without enforcing a secure sandbox, so an authenticated user with the ChangeMissionDatabase privilege could override an existing Python algorithm's logic through the mission database REST API and import and execute arbitrary Java classes such as java.lang.Runtime to achieve remote code execution on the underlying host operating system. This issue is fixed in versions 5.12.7 and 5.13.0, which disable algorithm editing by default.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46621 has been found in org.yamcs:yamcs-core.
Attackers can target a specific entry point like ChangeMissionDatabase over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: upgrade org.yamcs:yamcs-core to 5.12.7 or later.
If unsure, ask your IT team or search "org.yamcs:yamcs-core CVE-2026-46621" on the vendor's site.
CVE-2026-46621 (org.yamcs:yamcs-core) — CWE-94 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ChangeMissionDatabase / AlgorithmManager / ScriptAlgorithmExecutorFactory / ScriptEngine
Patched: 5.12.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in org.yamcs:yamcs-core. Attackers reach the vulnerable code path via ChangeMissionDatabase.
Check the vendor advisory for the affected versions of org.yamcs:yamcs-core. Attack surface: ChangeMissionDatabase / AlgorithmManager / ScriptAlgorithmExecutorFactory / ScriptEngine.
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover.
Update to 5.12.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.yamcs:yamcs-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.yamcs:yamcs-core to 5.12.7ステージング環境で 5.12.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com