# CVE-2026-108858: Predibase LoRAX through 0.12.1 API Token Exposure via Router Logs

> Attackers with log access can recover private API tokens from LoRAX router logs, potentially leading to unauthorized account access.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/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:** 13 Oct 2026
- **Also known as:** GHSA-mqw3-26gg-6g3w

## What is CVE-2026-108858?

CVE-2026-108858 is a medium-severity vulnerability in Predibase LoRAX, 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

Predibase LoRAX through 0.12.1 contains a sensitive information exposure vulnerability that writes the caller-supplied api_token from POST /generate request bodies into router logs. Attackers with access to router logs or OTLP trace backends can recover other users' private-adapter tokens recorded through the instrumented GenerateParameters span field.

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

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


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

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

## Is CVE-2026-108858 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108858 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108858 is a medium-severity vulnerability in Predibase LoRAX, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108858 exists.

Affected product: Predibase LoRAX. 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-108858/ (Markdown: https://insights.sbomify.com/CVE-2026-108858/index.md)
```

## Sources

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

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