← Back
CVE-2026-55545
medium
CVSS 6.5
Vulnerability in org.yamcs:yamcs-core (CVE-2026-55545)
Summary
vulnerability in org.yamcs:yamcs-core (CVE-2026-55545). Confidential information can be exposed externally. Exploitable via ``packets``. Mitigation: upgrade to `5.13.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55545** has been found in org.yamcs:yamcs-core.
Attackers can target a specific entry point like ``packets`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade org.yamcs:yamcs-core to **5.13.2** or later.
If unsure, ask your IT team or search "org.yamcs:yamcs-core CVE-2026-55545" on the vendor's site.
CVE-2026-55545 (org.yamcs:yamcs-core) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `packets` / `PacketsApi.subscribePackets` / `ReadPacket` / `ProcessingApi.subscribeAlgorithmStatus`
Patched: `5.13.2` — 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
**A vulnerability** (CWE-862) exists in org.yamcs:yamcs-core. Attackers reach the vulnerable code path via ``packets`` without authentication.
📍 Affected scope
org.yamcs:yamcs-core — . Attack surface: `packets` / `PacketsApi.subscribePackets` / `ReadPacket` / `ProcessingApi.subscribeAlgorithmStatus`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **5.13.2**.
🛡️ 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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.yamcs:yamcs-core to 5.13.2ステージング環境で 5.13.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.yamcs:yamcs-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.13.2"}]}]