Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55521 high CVSS 8.8

Vulnerability in org.yamcs:yamcs-core (CVE-2026-55521)

Summary

Vulnerability in org.yamcs:yamcs-core (CVE-2026-55521). Successful exploitation can lead to full system takeover. Exploitable via SystemPrivilege. Mitigation: upgrade to 5.12.8 or later.

Original description

The description as published by the source.

Summary

Multiple Missing Function Level Access Control vulnerabilities exist in the Yamcs Core API. These vulnerabilities allow any authenticated user, regardless of their assigned roles or privileges (e.g., an unprivileged "Guest"), to bypass intended access controls. An attacker can exploit these flaws to extract sensitive telemetry metadata, disrupt satellite communication link protocols (COP-1), and manipulate the global simulation time, severely impacting the confidentiality, integrity, and availability of the system.

Details

Yamcs utilizes a robust Role-Based Access Control (RBAC) model with SystemPrivilege and ObjectPrivilege to restrict administrative actions and data retrieval. However, three critical API controllers completely omit these authorization checks before executing internal business logic:

  1. IndexesApi.java (Information Disclosure): Unlike PacketsApi.java, which filters results using ctx.user.hasObjectPrivilege(ObjectPrivilegeType.ReadPacket, packetName), methods in IndexesApi (such as listPacketIndex and listEventIndex) directly retrieve and return archive records from the CcsdsTmIndex without verifying if the user has the required Object Privileges.
  2. Cop1Api.java (Denial of Service / Integrity): Modifying the COP-1 telecommand protocol state is an administrative action requiring SystemPrivilege.ControlLinks. However, endpoints in Cop1Api (e.g., disable, resume, initialize, updateConfig) process link…

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-55521 has been found in org.yamcs:yamcs-core.
Attackers can target a specific entry point like SystemPrivilege over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/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-55521" on the vendor's site.

CVE-2026-55521 (org.yamcs:yamcs-core) — CWE-862 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: SystemPrivilege / ObjectPrivilege / IndexesApi.java / PacketsApi.java
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

A vulnerability (CWE-862) exists in org.yamcs:yamcs-core. Attackers reach the vulnerable code path via SystemPrivilege.

📍 Affected scope

Check the vendor advisory for the affected versions of org.yamcs:yamcs-core. Attack surface: SystemPrivilege / ObjectPrivilege / IndexesApi.java / PacketsApi.java.

🔥 Severity

Severity: High (CVSS 8.8/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 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.12.8

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

  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":"0"},{"fixed":"5.12.8"}]}]

References

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