CVE-2026-108858: Predibase LoRAX through 0.12.1 API Token Exposure via Router Logs
Predibase LoRAX through 0.12.1 contains a sensitive information exposure vulnerability that writes the caller-supplied apitoken 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.
Affected Software
Event History
Frequently Asked Questions
Who can realistically recover exposed tokens?
Any user or service with access to LoRAX router logs or an OTLP trace backend receiving the router's telemetry can recover api_token values submitted by other users in POST /generate requests.
What must an attacker be able to do to exploit this issue?
The attacker needs access to recorded router logs or OTLP traces. They do not need to interact with the target user's request directly if the token has already been captured in the GenerateParameters span field.
Which requests may expose credentials?
POST /generate requests that include a caller-supplied api_token may have that token written to router logs and instrumented tracing data. The exposed value is described as a private-adapter token.
How can I determine whether tokens may already be exposed?
Review router logs and OTLP trace backends for GenerateParameters span fields associated with POST /generate activity, and check whether api_token values were retained. Any retained tokens should be treated as exposed to principals able to access those logging or tracing systems.