Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46562 critical CVSS 9.8

Code Injection in org.yamcs:yamcs-core (CVE-2026-46562)

Summary

Code injection in org.yamcs:yamcs-core (CVE-2026-46562). Successful exploitation can lead to full system takeover. Exploitable via PATCH /api/mdb/{instance}/{processor}/algorithms/{name. Mitigation: upgrade to 5.12.7 or later.

Original description

The description as published by the source.

Remote Code Execution via Mission Database algorithm override

Summary

The Nashorn ScriptEngine used to evaluate user-supplied algorithm text in MdbOverrideApi.updateAlgorithm is constructed without a ClassFilter, allowing a user with the ChangeMissionDatabase privilege to execute arbitrary Java code on the Yamcs server. In Yamcs's default configuration (no security.yaml), the built-in guest user has superuser=true, so the vulnerability is reachable without authentication.

Details

Vulnerable file: yamcs-core/src/main/java/org/yamcs/algorithms/ScriptAlgorithmExecutorFactory.java

// L46-53  Nashorn engine obtained without a ClassFilter
ScriptEngineFactory factory = scriptEngineManager.getEngineFactories().stream()
        .filter(candidate -> !JDK_BUILTIN_NASHORN_ENGINE_NAME.equals(candidate.getEngineName())
                && candidate.getNames().contains(language))
        .findFirst().orElse(null);
if (factory != null) {
    scriptEngine = factory.getScriptEngine();          // ← ClassFilter not supplied
}

// L109  user-supplied algorithm text reaches eval()
scriptEngine.eval(functionScript);

NashornScriptEngineFactory.getScriptEngine() accepts an optional ClassFilter that restricts which classes JavaScript can reach via Java.type(...). Yamcs passes no filter, so attacker-supplied JavaScript can reach any Java class — for example, Java.type("java.lang.Runtime").getRuntime().exec(...) runs arbitrary OS commands inside the…

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-46562 has been found in org.yamcs:yamcs-core.
Attackers can target a specific entry point like PATCH /api/mdb/{instance}/{processor}/algorithms/{name over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/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-46562" on the vendor's site.

CVE-2026-46562 (org.yamcs:yamcs-core) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: PATCH /api/mdb/{instance}/{processor}/algorithms/{name / PATCH /api/mdb-overrides/{instance}/{processor}/algorithms/{name / ScriptEngine / MdbOverrideApi.updateAlgorithm
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.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in org.yamcs:yamcs-core. Attackers reach the vulnerable code path via PATCH /api/mdb/{instance}/{processor}/algorithms/{name without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.yamcs:yamcs-core. Attack surface: PATCH /api/mdb/{instance}/{processor}/algorithms/{name / PATCH /api/mdb-overrides/{instance}/{processor}/algorithms/{name / ScriptEngine / MdbOverrideApi.updateAlgorithm.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 5.12.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual PATCH /api/mdb/{instance}/{processor}/algorithms/{name requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.yamcs:yamcs-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'PATCH /api/mdb/{instance}/{processor}/algorithms/{name' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで PATCH /api/mdb/{instance}/{processor}/algorithms/{name への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade org.yamcs:yamcs-core to 5.12.7

    ステージング環境で 5.12.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against PATCH /api/mdb/{instance}/{processor}/algorithms/{name on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.yamcs:yamcs-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.12.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details