Vulnerability in org.yamcs:yamcs-core (CVE-2026-55548)
Summary
Vulnerability in org.yamcs:yamcs-core (CVE-2026-55548). Risk of unauthorized operations or information disclosure. Exploitable via PacketsApi.exportPackets. Mitigation: upgrade to 5.12.8 or later.
Original description
The description as published by the source.
Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, the PacketsApi.exportPackets endpoint in yamcs-core/src/main/java/org/yamcs/http/api/PacketsApi.java failed to enforce object-level ReadPacket privileges when a request omitted specific packet names: with an empty name list the ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet) call passed over an empty set, no WHERE pname IN filter was applied to the resulting SELECT * FROM tm query, and the onTuple handler streamed every retrieved packet without any per-row authorization check, so a low-privileged or zero-privilege authenticated user could dump the entire raw telemetry packet archive and bypass the role-based access control model. This issue is fixed in versions 5.12.8 and 5.13.2, which enforce per-packet ReadPacket checks in exportPackets.
Source: NIST National Vulnerability Database 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-55548 has been found in org.yamcs:yamcs-core.
Attackers can target a specific entry point like PacketsApi.exportPackets over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/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-55548" on the vendor's site.
CVE-2026-55548 (org.yamcs:yamcs-core) — CWE-284 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PacketsApi.exportPackets / ReadPacket / exportPackets / nameSet
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.
A vulnerability (CWE-284) exists in org.yamcs:yamcs-core. Attackers reach the vulnerable code path via PacketsApi.exportPackets.
Check the vendor advisory for the affected versions of org.yamcs:yamcs-core. Attack surface: PacketsApi.exportPackets / ReadPacket / exportPackets / nameSet.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 5.12.8.
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.8ステージング環境で 5.12.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com