← Back
CVE-2026-55511
critical
CVSS 9.1
Code Injection in org.yamcs:yamcs-core (CVE-2026-55511)
Summary
code injection in org.yamcs:yamcs-core (CVE-2026-55511). Successful exploitation can lead to full system takeover. Exploitable via `POST /api/archive/{instance}`. Mitigation: upgrade to `5.12.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55511** has been found in org.yamcs:yamcs-core.
Attackers can target a specific entry point like `POST /api/archive/{instance}` 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.8** or later.
If unsure, ask your IT team or search "org.yamcs:yamcs-core CVE-2026-55511" on the vendor's site.
CVE-2026-55511 (org.yamcs:yamcs-core) — CWE-94 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/archive/{instance} / GET /api/instances / POST /auth/token / GET /api/user
Patched: `5.12.8` — 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 `POST /api/archive/{instance}` without authentication.
📍 Affected scope
org.yamcs:yamcs-core — . Attack surface: POST /api/archive/{instance} / GET /api/instances / POST /auth/token / GET /api/user.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **5.12.8**.
🛡️ 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 `POST /api/archive/{instance}` requests with malformed payloads or SQL meta-characters. Run `grep -r 'org.yamcs:yamcs-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.yamcs:yamcs-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.yamcs:yamcs-core` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/archive/{instance}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/archive/{instance}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade org.yamcs:yamcs-core to 5.12.8ステージング環境で 5.12.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/archive/{instance} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.yamcs:yamcs-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.12.8"}]}]