cve.bz

CVE-2026-108574 berriai litellm: Improper Authorization

2.1 lowEPSS 0.2%

Low (2.1) in berriai litellm. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw has been found in BerriAI LiteLLM up to 1.95.0. Affected by this issue is the function ui_view_session_spend_logs of the file litellm/proxy/spend_tracking/spend_management_endpoints.py of the component Spend Tracking. Executing a manipulation of the argument session_id can lead to authorization bypass. It is possible to launch the attack remotely. The exploit has been published and may be used. Upgrading to version 1.96.0 can resolve this issue. This patch is called 722d9ffa4f6c5ae15702ab9ab2c5f6bf1688308b. The affected component should be upgraded.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-285 Improper Authorization
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-108574 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-108574?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-108574?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-108574 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
BerriAI LiteLLM1.0
BerriAI LiteLLM1.1
BerriAI LiteLLM1.2
BerriAI LiteLLM1.3
BerriAI LiteLLM1.4
BerriAI LiteLLM1.5
BerriAI LiteLLM1.6
BerriAI LiteLLM1.7
BerriAI LiteLLM1.8
BerriAI LiteLLM1.9
BerriAI LiteLLM1.10
BerriAI LiteLLM1.11
BerriAI LiteLLM1.12
BerriAI LiteLLM1.13
BerriAI LiteLLM1.14
BerriAI LiteLLM1.15
BerriAI LiteLLM1.16
BerriAI LiteLLM1.17
BerriAI LiteLLM1.18
BerriAI LiteLLM1.19
BerriAI LiteLLM1.20
BerriAI LiteLLM1.21
BerriAI LiteLLM1.22
BerriAI LiteLLM1.23
BerriAI LiteLLM1.24
BerriAI LiteLLM1.25
BerriAI LiteLLM1.26
BerriAI LiteLLM1.27
BerriAI LiteLLM1.28
BerriAI LiteLLM1.29
BerriAI LiteLLM1.30
BerriAI LiteLLM1.31
BerriAI LiteLLM1.32
BerriAI LiteLLM1.33
BerriAI LiteLLM1.34
BerriAI LiteLLM1.35
BerriAI LiteLLM1.36
BerriAI LiteLLM1.37
BerriAI LiteLLM1.38
BerriAI LiteLLM1.39
BerriAI LiteLLM1.40
BerriAI LiteLLM1.41
BerriAI LiteLLM1.42
BerriAI LiteLLM1.43
BerriAI LiteLLM1.44
BerriAI LiteLLM1.45
BerriAI LiteLLM1.46
BerriAI LiteLLM1.47
BerriAI LiteLLM1.48
BerriAI LiteLLM1.49
BerriAI LiteLLM1.50
BerriAI LiteLLM1.51
BerriAI LiteLLM1.52
BerriAI LiteLLM1.53
BerriAI LiteLLM1.54
BerriAI LiteLLM1.55
BerriAI LiteLLM1.56
BerriAI LiteLLM1.57
BerriAI LiteLLM1.58
BerriAI LiteLLM1.59
BerriAI LiteLLM1.60
BerriAI LiteLLM1.61
BerriAI LiteLLM1.62
BerriAI LiteLLM1.63
BerriAI LiteLLM1.64
BerriAI LiteLLM1.65
BerriAI LiteLLM1.66
BerriAI LiteLLM1.67
BerriAI LiteLLM1.68
BerriAI LiteLLM1.69
BerriAI LiteLLM1.70
BerriAI LiteLLM1.71
BerriAI LiteLLM1.72
BerriAI LiteLLM1.73
BerriAI LiteLLM1.74
BerriAI LiteLLM1.75
BerriAI LiteLLM1.76
BerriAI LiteLLM1.77
BerriAI LiteLLM1.78
BerriAI LiteLLM1.79
BerriAI LiteLLM1.80
BerriAI LiteLLM1.81
BerriAI LiteLLM1.82
BerriAI LiteLLM1.83
BerriAI LiteLLM1.84
BerriAI LiteLLM1.85
BerriAI LiteLLM1.86
BerriAI LiteLLM1.87
BerriAI LiteLLM1.88
BerriAI LiteLLM1.89
BerriAI LiteLLM1.90
BerriAI LiteLLM1.91
BerriAI LiteLLM1.92
BerriAI LiteLLM1.93
BerriAI LiteLLM1.94
BerriAI LiteLLM1.95.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A MODERATE severity authorization bypass flaw was found in the BerriAI LiteLLM spend tracking component. The ui_view_session_spend_logs function in litellm/proxy/spend_tracking/spend_management_endpoints.py does not properly verify that the requesting user is authorized to view a given session, so an authenticated remote attacker can manipulate the session_id parameter to view spend tracking logs and usage metrics belonging to other users' sessions. The impact is limited to the confidentiality of spend and usage data; there is no impact on integrity or availability (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). Red Hat products that bundle litellm, including Red Hat OpenShift AI, Ansible Automation Platform lightspeed chatbot offerings, Lightspeed Core, and related Lightspeed/Insights and Ansible Services offerings, are affected. Because the impact is MODERATE with a CVSS score below 7.0, fixes for these products are deferred and no trackers are being filed; the residual risk is that an authenticated user may read spend tracking logs and usage metrics of other users' sessions. The services-lightspeed-agent-google-cloud stream is out of support scope. Red Hat rates this issue MODERATE (CVSS 4.3); the upstream CVSS 4.0 score is 2.1 (LOW), while the upstream CVSS 3.1 score of 4.3 matches the Red Hat assessment.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream LiteLLM project has addressed this flaw in version 1.96.0; upgrading to a release that includes this fix resolves the issue for direct upstream deployments.

ProductPackageStateAdvisory
Lightspeed Corelightspeed-core/lightspeed-stack-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-chatbot-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-chatbot-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-llama-stack-core-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cuda-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-108574.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-285 (16).

References

Check your stackJSON