Yamcs-Core (5.13.0-5.13.1) - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/yamcs-core-5.13.0-5.13.1/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 28 Aug 2026 21:18:21 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgUnauthenticated Directory Traversal in Yamcshttps://feed.craftedsignal.io/briefs/2026-08-yamcs-traversal/Fri, 28 Aug 2026 21:18:21 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-yamcs-traversal/Yamcs versions prior to 5.11.13 contain an unauthenticated directory traversal vulnerability in the HTTP request handling components that allows remote attackers to read arbitrary files from the underlying host.Yamcs versions prior to 5.11.13 are susceptible to an unauthenticated directory traversal vulnerability (CVE-2026-55552) residing in the HttpRequestHandler.java and StaticFileHandler.java components. This flaw allows remote, unauthenticated attackers to bypass intended directory restrictions by crafting specific HTTP requests containing traversal sequences. An attacker can leverage this to retrieve sensitive system files, configuration files, or other data residing on the host filesystem where Yamcs is deployed. Given the nature of the application as a mission control system, exposure of sensitive configuration or authentication files poses a significant risk to the integrity and confidentiality of the entire environment.

Impact

Successful exploitation grants an unauthenticated attacker the ability to read arbitrary files from the filesystem of the host running the Yamcs service. This can lead to the exfiltration of credentials, system configuration details, or sensitive operational data, potentially facilitating further unauthorized access or complete system compromise.

Recommendation

  1. Upgrade Yamcs to version 5.11.13 or later immediately to patch CVE-2026-55552.
  2. Implement network-level access controls to restrict access to the Yamcs management interface to known, trusted IP ranges.
  3. Deploy the provided Sigma rule to web server access logs to detect directory traversal attempts.
  4. Perform a log review for any historical GET requests to the Yamcs interface containing '..' or unusual path indicators.
]]>highadvisoryweb-vulnerabilitydirectory-traversalcve-2026-55552privilege-escalationweb-application-vulnerability