Lorax
Monthly
Predibase LoRAX through 0.12.1 can expose private-adapter API tokens because the router writes the caller-supplied api_token from POST /generate request bodies into router logs and instrumented GenerateParameters spans, making the tokens recoverable by anyone who can read those logs or the OTLP trace backend. Exploitation is not a raw network attack against the inference API: the supplied CVSS 4.0 vector and our independent CVSS 3.1 assessment both require local/low-privileged access (AV:L, PR:L) and show confidentiality-only impact, while integrity and availability are unaffected. No public exploit identified at time of analysis, and the practical risk is limited to deployments that log requests or export traces with the GenerateParameters instrumentation active and whose users send api_token for private/gated adapters.
Predibase LoRAX through 0.12.1 can expose private-adapter API tokens because the router writes the caller-supplied api_token from POST /generate request bodies into router logs and instrumented GenerateParameters spans, making the tokens recoverable by anyone who can read those logs or the OTLP trace backend. Exploitation is not a raw network attack against the inference API: the supplied CVSS 4.0 vector and our independent CVSS 3.1 assessment both require local/low-privileged access (AV:L, PR:L) and show confidentiality-only impact, while integrity and availability are unaffected. No public exploit identified at time of analysis, and the practical risk is limited to deployments that log requests or export traces with the GenerateParameters instrumentation active and whose users send api_token for private/gated adapters.