CVE-2026-108574 PUBLISHED

BerriAI LiteLLM Spend Tracking spend_management_endpoints.py ui_view_session_spend_logs authorization

Assigner: VulDB
Reserved: 10.10.2026 Published: 11.10.2026 Updated: 11.10.2026

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.

Metrics

CVSS Vector: 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 Score: 5.3

Product Status

Vendor BerriAI
Product LiteLLM
Versions
  • Version 1.0 is affected
  • Version 1.1 is affected
  • Version 1.2 is affected
  • Version 1.3 is affected
  • Version 1.4 is affected
  • Version 1.5 is affected
  • Version 1.6 is affected
  • Version 1.7 is affected
  • Version 1.8 is affected
  • Version 1.9 is affected
  • Version 1.10 is affected
  • Version 1.11 is affected
  • Version 1.12 is affected
  • Version 1.13 is affected
  • Version 1.14 is affected
  • Version 1.15 is affected
  • Version 1.16 is affected
  • Version 1.17 is affected
  • Version 1.18 is affected
  • Version 1.19 is affected
  • Version 1.20 is affected
  • Version 1.21 is affected
  • Version 1.22 is affected
  • Version 1.23 is affected
  • Version 1.24 is affected
  • Version 1.25 is affected
  • Version 1.26 is affected
  • Version 1.27 is affected
  • Version 1.28 is affected
  • Version 1.29 is affected
  • Version 1.30 is affected
  • Version 1.31 is affected
  • Version 1.32 is affected
  • Version 1.33 is affected
  • Version 1.34 is affected
  • Version 1.35 is affected
  • Version 1.36 is affected
  • Version 1.37 is affected
  • Version 1.38 is affected
  • Version 1.39 is affected
  • Version 1.40 is affected
  • Version 1.41 is affected
  • Version 1.42 is affected
  • Version 1.43 is affected
  • Version 1.44 is affected
  • Version 1.45 is affected
  • Version 1.46 is affected
  • Version 1.47 is affected
  • Version 1.48 is affected
  • Version 1.49 is affected
  • Version 1.50 is affected
  • Version 1.51 is affected
  • Version 1.52 is affected
  • Version 1.53 is affected
  • Version 1.54 is affected
  • Version 1.55 is affected
  • Version 1.56 is affected
  • Version 1.57 is affected
  • Version 1.58 is affected
  • Version 1.59 is affected
  • Version 1.60 is affected
  • Version 1.61 is affected
  • Version 1.62 is affected
  • Version 1.63 is affected
  • Version 1.64 is affected
  • Version 1.65 is affected
  • Version 1.66 is affected
  • Version 1.67 is affected
  • Version 1.68 is affected
  • Version 1.69 is affected
  • Version 1.70 is affected
  • Version 1.71 is affected
  • Version 1.72 is affected
  • Version 1.73 is affected
  • Version 1.74 is affected
  • Version 1.75 is affected
  • Version 1.76 is affected
  • Version 1.77 is affected
  • Version 1.78 is affected
  • Version 1.79 is affected
  • Version 1.80 is affected
  • Version 1.81 is affected
  • Version 1.82 is affected
  • Version 1.83 is affected
  • Version 1.84 is affected
  • Version 1.85 is affected
  • Version 1.86 is affected
  • Version 1.87 is affected
  • Version 1.88 is affected
  • Version 1.89 is affected
  • Version 1.90 is affected
  • Version 1.91 is affected
  • Version 1.92 is affected
  • Version 1.93 is affected
  • Version 1.94 is affected
  • Version 1.95.0 is affected
  • Version 1.96.0 is unaffected

Credits

  • Gabriel Alves (VulDB User) reporter
  • VulDB Vulnerability Moderation Team coordinator

References

Problem Types

  • Authorization Bypass CWE
  • Improper Authorization CWE