# LaunchServer FileServerHandler has an unauthenticated path traversal issue Advisory record · `GHSA-5g75-477j-2c2f` - **Identifiers:** `GHSA-5g75-477j-2c2f` · `CVE-2026-54617` - **State:** Confirmed - **Severity:** CVSS 9.8 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html) - **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) - **Published:** 2 Jul 2026 - **Updated:** 2 Jul 2026 - **Reviewed by a person:** No 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. ## Critical Critical, because: - CVSS score 9.8: 9.0 or more. How we decide what’s critical: ## Affected packages - `pro.gravit.launcher:launchserver-api` (Maven): affected `<=5.7.11`; no fixed version yet ## 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 - 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from 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 - 31 Oct 2026, 14:20 UTC: First seen by agentprime - 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5g75-477j-2c2f) ## Sources - [GitHub Advisory Database: GHSA-5g75-477j-2c2f](https://github.com/advisories/GHSA-5g75-477j-2c2f) - [OSV: GHSA-5g75-477j-2c2f](https://osv.dev/vulnerability/GHSA-5g75-477j-2c2f) - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .