Yamcs up to 5.11.12 StaticFileHandler StaticFileHandler.java StaticFileHandler.locateFile path traversal

Summaryinfo

A vulnerability was found in Yamcs up to 5.11.12. It has been classified as problematic. Impacted is the function StaticFileHandler.locateFile of the file yamcs-core/src/main/java/org/yamcs/http/StaticFileHandler.java of the component StaticFileHandler. The manipulation leads to path traversal. This vulnerability is listed as CVE-2026-55552. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Yamcs up to 5.11.12. It has been rated as problematic. This issue affects the function StaticFileHandler.locateFile of the file yamcs-core/src/main/java/org/yamcs/http/StaticFileHandler.java of the component StaticFileHandler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-55552 since 06/17/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 5.11.13 or 5.12.0 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• Yamcs

Version

• 5.11.0
• 5.11.1
• 5.11.2
• 5.11.3
• 5.11.4
• 5.11.5
• 5.11.6
• 5.11.7
• 5.11.8
• 5.11.9
• 5.11.10
• 5.11.11
• 5.11.12

Website

• Product: https://github.com/yamcs/yamcs/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion