# CVE-2026-108754: GPT-Load through 1.4.11 Cleartext Proxy Key Logging via Access Logger

> Attackers with log access can recover cleartext proxy keys from GPT-Load logs, enabling unauthorized use of API groups.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-cg67-pj93-c6m6

## What is CVE-2026-108754?

CVE-2026-108754 is a medium-severity vulnerability in tbphp gpt-load, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GPT-Load through 1.4.11 contains a cleartext logging vulnerability that exposes client proxy keys because the Gin Logger middleware records the raw query string before extractAuthKey strips the key parameter. Attackers with read access to console logs or ./data/logs/app.log can recover proxy keys from Gemini-style requests and use them against the corresponding group.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-108754?


## How do I fix CVE-2026-108754?

No fix has been published for CVE-2026-108754 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108754 being exploited?

There is no known exploitation of CVE-2026-108754 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108754 and fix it if it is affected.

What it is: CVE-2026-108754 is a medium-severity vulnerability in tbphp gpt-load, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108754 in the wild and no public exploit code.

Affected product: tbphp gpt-load. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108754/ (Markdown: https://insights.sbomify.com/CVE-2026-108754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108754
- OSV: https://osv.dev/vulnerability/CVE-2026-108754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108754/
Summaries are generated and may contain mistakes; the official description above is the record.