/

CVE-2026-54617

Severity:

CRITICAL RISK

(9.8)

Path Traversal (CWE-22) in GravitLauncher File Server

CVE-2026-54617

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22, CWE-200, CWE-522

Impact:

Sensitive Information Disclosure and Authentication Bypass

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

GravitLauncher contains a path traversal vulnerability in its default LaunchServer file server that can allow unauthenticated remote clients to read files outside the intended updates directory. Exposed signing keys, token material, or database credentials could enable forged administrative tokens, authentication bypass, and broader server compromise when the file server is directly reachable.

Affected context

The issue occurs in LaunchServer deployments where the default file server is enabled and reachable through a path that preserves a request target without a leading slash. The vulnerable handler removes the first request-target character and resolves the remainder against the configured updates directory without consistently normalizing the resulting path or verifying that it remains within the intended directory. Normalizing application-layer proxies may reduce exposure, while direct exposure and some lower-layer proxy arrangements may leave the file server reachable.

Exploit preconditions

  • Attack surface: The LaunchServer file server, commonly exposed on its configured file-server port
  • Required access: No authentication is generally required if the file-server endpoint is network-reachable
  • Trigger point: Processing of a specially formed HTTP request target by FileServerHandler
  • Why exploitation is possible: Path components are resolved against the updates directory without sufficient normalization and containment validation, allowing access to files outside the intended document root

Why this happens

The underlying bug is improper limitation of a pathname to a restricted directory, mapping to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The handler modifies the request target and resolves it against the updates directory, but does not reliably canonicalize the resulting path and verify that the canonical result remains beneath the permitted root. This insecure pattern permits attacker-controlled path components to influence filesystem access. The resulting disclosure can also relate to CWE-200 and CWE-522 when sensitive files and authentication-related secrets become readable.

Potential impact

  • An attacker may read arbitrary files accessible to the LaunchServer process
  • Signing keys and token material could be disclosed
  • Database credentials and configuration secrets may be exposed
  • Attackers could forge administrative access tokens
  • Authentication controls could be bypassed
  • The LaunchServer or connected services could be compromised

General mitigation guidance

Mitigation generally focuses on enforcing a strict filesystem trust boundary and reducing the exposure of sensitive runtime files.

Common defensive patterns include:

  • Canonicalizing requested paths before filesystem access
  • Verifying that canonical paths remain within the intended document root
  • Rejecting traversal components and malformed request targets by default
  • Serving files through an allowlisted resource model rather than arbitrary filesystem resolution
  • Binding file-serving interfaces to trusted networks or keeping them behind access-controlled gateways
  • Disabling unnecessary file-serving functionality
  • Storing signing keys, tokens, and database credentials outside web-accessible directories
  • Running the LaunchServer process with the minimum filesystem permissions required
  • Rotating potentially exposed credentials and invalidating affected tokens
  • Applying proxy policies that reject ambiguous or non-normalized request targets

How teams detect issues like this

Organizations can assess for this issue through:

  • Static analysis checks for filesystem joins that use request-controlled paths without canonical containment checks
  • Code review of handlers that strip, decode, normalize, or reconstruct HTTP request targets
  • Tests covering parent-directory components, encoded separators, alternate request-target forms, and proxy normalization differences
  • Runtime monitoring for unexpected file-server requests and access attempts involving sensitive filenames
  • File-access auditing for reads outside the configured updates directory
  • Configuration policy checks ensuring file-server endpoints are not unnecessarily exposed and that secret directories are inaccessible to service processes
  • Automated security review tools that flag path traversal and unrestricted file-read patterns

Sources

SourceLink
github.comgithub.com/GravitLauncher/Launcher/commit/8114a1d4cfbcaab4c1c337d921597805d71dee3b
github.comgithub.com/GravitLauncher/Launcher/releases/tag/v5.7.12
github.comgithub.com/GravitLauncher/Launcher/security/advisories/GHSA-5g75-477j-2c2f

Frequently asked

questions

It may be exploitable remotely without authentication when the LaunchServer file server is directly reachable or exposed through a proxy that preserves the relevant request form.

The attacker generally needs network access to the file-server endpoint. A separate user account or prior authentication may not be required, although network segmentation and proxy behavior can affect exploitability.

Enforce canonical path resolution followed by a strict containment check, reject ambiguous request targets, and expose only explicitly allowlisted files rather than arbitrary paths.

Use security-focused filesystem APIs, keep secrets outside served directories, apply least-privilege service accounts, test proxy and application parsing consistently, and monitor file access beyond approved resource roots.

Find out what's already
exploitable in your codebase.