Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55552 high CVSS 7.5

Path Traversal in org.yamcs:yamcs-core (CVE-2026-55552)

Summary

Path traversal in org.yamcs:yamcs-core (CVE-2026-55552). Confidential information can be exposed externally. Mitigation: upgrade to 5.12.0 or later.

Original description

The description as published by the source.

Attack type: 

Unauthenticated remote 

Impact:

Attackers can access any system files from the underlying host.

Affected components: HttpRequestHandler.java, StaticFileHandler.java

An Unauthenticated Directory Traversal vulnerability exists in Yamcs <=5.8.6, allowing anyone to access any file on the underlying operating system. This allows unauthenticated attackers to download sensitive files and data.

Steps to Reproduce:

  1. Start Yamcs and login as a user
  2. Paste the following URL in the browser and press enter:
http://localhost:8090//etc/passwd
  1. The /etc/passwd file will be downloaded.

Acknowledgements

This vulnerability was discovered by Abderrahim Dahmani while solving a STARPWN 2025 CTF challenge at DEFCON 33 offered by VisionSpace Technologies.

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-55552 has been found in org.yamcs:yamcs-core.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade org.yamcs:yamcs-core to 5.12.0 or later.
If unsure, ask your IT team or search "org.yamcs:yamcs-core CVE-2026-55552" on the vendor's site.

CVE-2026-55552 (org.yamcs:yamcs-core) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 5.12.0 — 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

Path traversal (CWE-22) exists in org.yamcs:yamcs-core.

📍 Affected scope

Check the vendor advisory for the affected versions of org.yamcs:yamcs-core.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.12.0.

🛡️ 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.0

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

  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.0"}]}]

References

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