Advisory record · GHSA-5g75-477j-2c2f

LaunchServer FileServerHandler has an unauthenticated path traversal issue

CVSS 9.8 CriticalCriticalEPSS 0.035 · 89th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 2 Jul 2026, 20:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pro.gravit.launcher:launchserver-apiMaven<=5.7.11No fixed version yet
Identifiers
GHSA-5g75-477j-2c2f · CVE-2026-54617
Weakness (CWE)
CWE-22 · CWE-200 · CWE-522
Published
2 Jul 2026
Updated
2 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GravitLauncher LaunchServer versions up to and including 5.7.11 are affected by an unauthenticated path traversal in the HTTP file server handler. A remote attacker who can reach the server, with the default configuration on port 9274, can send a crafted request to read any file the server process can access, including signing keys and database credentials. The source reports that a read of the signing key would allow forging access tokens for any account. No fixed version is listed. Restricting access to the file server port with a firewall is the only mitigation the source describes.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.035, the 89th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.