Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Asset / scope: Yamcs 5.12.7 WebSocket topics (packets, algorithm-status, mdb-changes)

Summary

Several WebSocket subscription handlers do not perform the privilege check that their REST counterparts
enforce, so a principal subscribing over WebSocket receives data the REST API would have scoped or denied.

Root cause

  • packets (PacketsApi.subscribePackets) performs no ReadPacket check, while the REST siblings do
    (listPackets:128, streamPackets:256, subscribeContainers:538). A principal with a narrow
    ReadPacket scope receives the raw binary of all TM packets on the processor.
  • algorithm-status (ProcessingApi.subscribeAlgorithmStatus) performs no check, while REST
    getAlgorithmStatus enforces checkObjectPrivileges(ReadAlgorithm, ...) (:467).
  • mdb-changes (MdbOverrideApi.subscribeMdbChanges) performs no check, while base MDB reads require
    GetMissionDatabase.

Remediation

Bring each WebSocket subscription handler to parity with its REST sibling's privilege check
(ReadPacket, ReadAlgorithm, GetMissionDatabase). This is the same declarative fail-closed fix as
Report 1.

Supporting material

Subsystem source audit of the WS-vs-REST authorization parity. Available on request.

--

Disclosure and credit

This was found by Cipher / Causal Security - https://causalsecurity.com/. We are coordinating disclosure
via this report and request CVEs where you agree they qualify. We propose the 90-day window stated in your
s…

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-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.

📍 Affected scope

Check the vendor advisory for the affected versions of 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. 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
    Apply patch patch 
    Upgrade org.yamcs:yamcs-core to 5.13.2

    ステージング環境で 5.13.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

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

References

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