CVE-2026-54617
CRITICALEPSS 87th pctlDescription
GravitLauncher is an open-source Minecraft launcher based on sashok724's v3. Prior to 5.7.12, an unauthenticated remote actor can send a raw HTTP request target without a leading slash to the default LaunchServer file server on port 9274. FileServerHandler.channelRead0 in components/launchserver/src/main/java/pro/gravit/launchserver/socket/handlers/fileserver/FileServerHandler.java strips the first request-target character and resolves the remaining path against updatesDir without re-normalizing and verifying containment. This leaves parent-directory components in a no-leading-slash request and allows reading 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. A normalizing L7 proxy may block the primary request form, but direct exposure and L4/TCP proxies remain affected, and netty.fileServerEnabled is enabled by default. This issue is fixed in 5.7.12.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Elevated risk: more likely to be exploited than 87% of all known CVEs.
References
Related Vulnerabilities
Other CWE-22 (Path Traversal) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-23897 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-32315 | High | 8.6 | 100% | KEV | Fix |
| CVE-2022-29464 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-26086 | Medium | 5.3 | 100% | KEV | Fix |
| CVE-2021-22005 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2020-5902 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-54617?
No published fix for CVE-2026-54617 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-54617 being actively exploited?
Not that we know of. CVE-2026-54617 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 2.9% is the estimated probability that it will be exploited in the next 30 days. That is higher than 87% of all scored CVEs.
How severe is CVE-2026-54617?
CVE-2026-54617 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-54617
Markdown
[](https://tridentstack.com/cve/CVE-2026-54617)HTML
<a href="https://tridentstack.com/cve/CVE-2026-54617"><img src="https://tridentstack.com/cve/badge/CVE-2026-54617.svg" alt="CVE-2026-54617"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-24.