Host file disclosure via unnormalized static path
Published Aug 28, 2026 · Updated Aug 28, 2026
Path traversal in Yamcs before 5.12.0 allows remote attackers to read host files through unauthenticated static-file requests. StaticFileHandler.locateFile resolves the request path under each staticRoots entry but fails to normalize it and verify that its absolute form remains inside the root. A crafted path with traversal segments reaches any existing, non-hidden file readable by the Yamcs process; no account or user interaction is required.
Summary
What happened
Path traversal in Yamcs before 5.12.0 allows remote attackers to read host files through unauthenticated static-file requests. StaticFileHandler.locateFile resolves the request path under each staticRoots entry but fails to normalize it and verify that its absolute form remains inside the root. A crafted path with traversal segments reaches any existing, non-hidden file readable by the Yamcs process; no account or user interaction is required.
The record
- CVE
- CVE-2026-55552
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Space Applications Services
- Product
- Yamcs
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.12.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream static-file traversal reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo