Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-54617 – Unauthenticated Path Traversal Leading to Full Authentication Bypass – GravitLaunch

Be the first to know when new zero-days emerge:

Summary

CVE-2026-54617 is a critical unauthenticated path traversal vulnerability in GravitLauncher’s LaunchServer FileServerHandler component, which is exposed by default on port 9274. The flaw allows a remote, unauthenticated attacker to read arbitrary files on the server’s filesystem, including the server’s ECDSA signing key and database credentials, effectively enabling full authentication bypass and compromise of the LaunchServer instance. The issue carries a CVSS v3.1 base score of 9.8 (Critical) and affects all GravitLauncher LaunchServer versions prior to 5.7.12.

Technical details

  • Root cause: The FileServerHandler strips the leading character from the HTTP request target as part of its path-handling logic but does not properly normalize or validate the remainder of the path before serving files relative to the configured updatesDir. Sending a request target that omits the expected leading slash bypasses the directory containment check, allowing ../ sequences to traverse outside the intended directory.
  • Trigger conditions: No authentication or user interaction is required. The attacker only needs network access to the LaunchServer’s file-server port (default 9274) and can send a single crafted HTTP request (e.g. requesting ../../.keys/ecdsa_id without a leading slash).
  • Attack vector: Network (remote, pre-authentication).
  • Impact: Disclosure of sensitive files readable by the LaunchServer process, most critically:
    • The ECDSA private key (.keys/ecdsa_id) used to sign access JWTs, allowing an attacker to forge valid access tokens for any account, including administrators — a full authentication bypass.
    • The refresh-token salt (.keys/legacySalt).
    • LaunchServer.json, which may contain database credentials.
    • Any other file on disk readable by the server process, making this a generic arbitrary file-read primitive that can be leveraged for full server compromise, not just information disclosure.

Affected software

  • GravitLauncher LaunchServer — all versions up to and including 5.7.11
  • Fixed in GravitLauncher LaunchServer 5.7.12

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade GravitLauncher LaunchServer to version 5.7.12 or later, which fixes the path normalization and directory containment logic in FileServerHandler.
  • If immediate patching is not possible:
    • Restrict network access to the LaunchServer file-server port (default 9274) to trusted hosts only, using firewall rules or network segmentation.
    • Place the LaunchServer behind a reverse proxy or WAF configured to reject request paths containing traversal sequences or malformed request targets lacking a leading slash.
    • Rotate the ECDSA signing key (.keys/ecdsa_id), refresh-token salt (.keys/legacySalt), and any database credentials stored in LaunchServer.json if exposure cannot be ruled out, and invalidate existing issued tokens.
    • Monitor file-server access logs for anomalous requests targeting .keys/, LaunchServer.json, or containing ../ traversal patterns.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge