Skip to main content

CVE-2026-108858: Insertion of Sensitive Information into Log File in Predibase LoRAX

0
Medium
Published: 10/11/2026 (10/11/2026, 15:31:08 UTC)
Source: CVE Database V5
Vendor/Project: Predibase
Product: LoRAX

Description

Predibase LoRAX versions up to 0.12.1 have a vulnerability where the api_token from POST /generate requests is logged in router logs. This exposes sensitive tokens to anyone with access to these logs or OTLP trace backends. The vulnerability can lead to unauthorized disclosure of private adapter tokens. The CVSS 4.0 score rates this as a medium severity issue.

CVSS v4.0

Score 6.8medium

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

Predibase

LoRAX

Affected versions
>=0 <=0.12.1
GitHub Actionsmore threats →cve
LoRAX
pkg:github/LoRAX
Affected versions
>=0 <=0.12.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/11/2026, 14:03:46 UTC

Technical Analysis

CVE-2026-108858 describes a sensitive information exposure vulnerability in Predibase LoRAX through version 0.12.1. The issue arises because the api_token supplied by callers in POST /generate request bodies is written into router logs, specifically within the instrumented GenerateParameters span field. An attacker with access to router logs or OTLP trace backends can extract other users' private adapter tokens from these logs. This vulnerability has a CVSS 4.0 base score of 6.8, indicating a medium severity risk. There is no information about an available patch or vendor advisory specifying remediation.

Potential Impact

The vulnerability allows an attacker with access to router logs or OTLP trace backends to obtain sensitive api_tokens belonging to other users. This exposure can lead to unauthorized use of private adapter tokens, potentially compromising user accounts or services relying on these tokens. There is no indication of privilege escalation or direct remote exploitation without log access.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to router logs and OTLP trace backends to trusted personnel only to prevent unauthorized token disclosure.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-10-11T13:06:48.900Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6acb93d32cdf04f656d7076e

Added to database: 10/11/2026, 13:49:07 UTC

Last enriched: 10/11/2026, 14:03:46 UTC

Last updated: 10/11/2026, 21:33:07 UTC

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses