CVE-2026-54617 GravitLauncher CVE debrief

Who should care

Administrators and users of GravitLauncher, especially those with exposed LaunchServer instances, should review and apply the patch in version 5.7.12. They should also restrict access to the LaunchServer file server and monitor for suspicious activity to prevent potential exposure of signing keys and database credentials, and possible authentication bypass and forged administrative access tokens.

Why it matters

This vulnerability allows unauthenticated remote file reads, potentially exposing sensitive information and enabling authentication bypass.

• Potential exposure of signing keys and database credentials
• Possible authentication bypass and forged administrative access tokens
• Potential data theft or unauthorized access

Technical summary

An unauthenticated remote actor can send a raw HTTP request to the default LaunchServer file server on port 9274, allowing reading of any file accessible to the LaunchServer process, including .keys/ecdsa_id, .keys/legacySalt, and LaunchServer.json. Disclosure of those files can expose signing keys, refresh-token material, and database credentials, enabling forged administrative access tokens and full authentication bypass. This leaves parent-directory components in a no-leading-slash request and allows reading any file accessible to the LaunchServer process.

Defensive priority

High

Recommended defensive actions

• Review and apply the patch in version 5.7.12
• Restrict access to the LaunchServer file server
• Monitor for suspicious activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. The issue is fixed in version 5.7.12. The vulnerability allows unauthenticated remote file reads, potentially exposing sensitive information and enabling authentication bypass. Disclosure of those files can expose signing keys, refresh-token material, and database credentials, enabling forged administrative access tokens and full authentication bypass. A normalizing L7 proxy may block the primary request form, but direct exposure and L4/TCP proxies remain affected, and

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.