Yamcs
Yamcs: Unauthenticated Directory Traversal
Yamcs is a mission control framework. Prior to 5.11.13, Yamcs StaticFileHandler.locateFile resolves an unauthenticated request path without using Path.normalize and Path.toAbsolutePath to confirm that the absolute path remains within the configured staticRoots. A path containing traversal segments can escape the intended web root and return an arbitrary readable host file. The flaw is in yamcs-core/src/main/java/org/yamcs/http/StaticFileHandler.java and can disclose sensitive operating-system and application data. This issue is fixed in version 5.11.13, and the 5.12 line is fixed from version 5.12.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 5.12.0
Fixed in 5.12.0
Mitigation
Upgrade yamcs to 5.12.0 or later.
References
- Vendor advisory github.com/yamcs/yamcs/security/advisories/GHS…
- Patch github.com/yamcs/yamcs/commit/c7dfd24e469ae108…
- Patch github.com/yamcs/yamcs/commit/f4bc588880c16684…
2 more
- Release notes github.com/yamcs/yamcs/releases/tag/yamcs-5.11…
- Release notes github.com/yamcs/yamcs/releases/tag/yamcs-5.12…
Timeline
Days relative to CVE publicationFirst public PoC 38 days after publication; not in CISA KEV. First PoC: nuclei template: Yamcs <=5.11.12 - Arbitrary File Read (nuclei template, 5 Oct 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Yamcs <=5.11.12 - Arbitrary File Read | 5 Oct 2026 | 14 Nov 2026 |