CVE-2026-54617

9.8

GravitLauncher · Launcher

A path traversal vulnerability in GravitLauncher allows unauthenticated remote attackers to read sensitive files, including credentials and cryptographic keys, via specially crafted HTTP requests.

Executive summary

A critical path traversal vulnerability in GravitLauncher versions prior to 5.7.12 allows unauthenticated remote attackers to access sensitive system files and achieve full authentication bypass.

Vulnerability

This is a path traversal flaw (CWE-22) residing in the FileServerHandler component. An unauthenticated remote attacker can bypass directory restrictions by sending a raw HTTP request without a leading slash, forcing the server to resolve paths outside the intended directory and expose critical files such as signing keys and database credentials.

Business impact

The exposure of cryptographic keys and database credentials grants an attacker the ability to forge administrative tokens, leading to a complete compromise of the LaunchServer environment. Given the CVSS score of 9.8, this vulnerability poses an extreme risk to confidentiality, integrity, and availability. Unauthorized access to these assets can result in total system takeover, data exfiltration, and significant reputational damage.

Remediation

Immediate Action: Upgrade GravitLauncher to version 5.7.12 or later immediately to resolve the directory traversal flaw.

Proactive Monitoring: Review server access logs for anomalous HTTP requests that lack a leading slash or contain directory traversal sequences like dot-dot-slash.

Compensating Controls: Deploy a Web Application Firewall (WAF) or a reverse proxy configured to normalize incoming HTTP requests and block non-standard request paths.

Exploitation status

Public Exploit Available: No (exploit_available unknown).

Analyst recommendation

This vulnerability represents a critical security failure that mandates immediate attention. System administrators must prioritize patching the LaunchServer component to version 5.7.12 to prevent potential unauthorized access and credential theft. Failure to remediate this issue exposes the entire infrastructure to full compromise by unauthenticated remote actors.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources