CVE-2026-35030

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, when JWT authentication is enabled (enable_jwt_auth: true), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters. This configuration option is not enabled by default. Most instances are not affected. An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user's cached token. On cache hit, the attacker inherits the legitimate user's identity and permissions. This affects deployments with JWT/OIDC authentication enabled. Fixed in v1.83.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

April 6, 2026

Last Modified

July 15, 2026

Advisory Details (7)

Auto-updated Sep 7, 2026
Patch available. Sources: github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35030.json
redhat

2455509 – (CVE-2026-35030) CVE-2026-35030 litellm: LiteLLM: Authentication bypass and privilege escalation via OIDC userinfo cache key collision

https://bugzilla.redhat.com/show_bug.cgi?id=2455509
redhat Patch Available

CVE-2026-35030 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-35030
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30056
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:28960
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13545
github Patch Available

Authentication bypass via OIDC userinfo cache key collision · Advisory · BerriAI/litellm · GitHub

Affected: v1.83.0. The cache key now uses the full hash of the JWT token.

https://github.com/BerriAI/litellm/security/advisories/GHSA-jjhc-v7c2-5hh6

Vendor Advisories for CVE-2026-35030(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17823100082026-06-25redhat
redhatrhoai/odh-llama-stack-core-rhel9:17818264062026-06-24redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17773985762026-05-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
litellm0.1.0 ... 1.9.dev0 (1101 versions)1.83.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 220 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 23:29 UTCOSV refresh
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 12:21 UTCVendor advisory
  4. 2026-08-16 08:24 UTCEG score recompute
  5. 2026-08-16 08:24 UTCVendor advisory
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 22:42 UTCVendor advisory
  9. 2026-08-14 18:46 UTCVendor advisory
  10. 2026-08-14 13:26 UTCVendor advisory
  11. 2026-08-14 09:29 UTCVendor advisory
  12. 2026-08-14 05:32 UTCEG score recompute
  13. 2026-08-14 05:32 UTCVendor advisory
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 09:44 UTCVendor advisory
  16. 2026-08-13 03:39 UTCVendor advisory
  17. 2026-08-12 23:42 UTCVendor advisory
  18. 2026-08-12 19:45 UTCEG score recompute
  19. 2026-08-12 19:45 UTCVendor advisory
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-11 23:53 UTCVendor advisory
  22. 2026-08-11 19:56 UTCEG score recompute
  23. 2026-08-11 19:56 UTCVendor advisory
  24. 2026-08-11 07:14 UTCVendor advisory
  25. 2026-08-11 03:18 UTCEG score recompute
  26. 2026-08-11 03:18 UTCVendor advisory
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 12:51 UTCVendor advisory
  29. 2026-08-10 08:40 UTCVendor advisory
  30. 2026-08-10 04:44 UTCVendor advisory
  31. 2026-08-10 00:47 UTCVendor advisory
  32. 2026-08-09 20:49 UTCVendor advisory
  33. 2026-08-09 16:52 UTCEG score recompute
  34. 2026-08-09 16:52 UTCVendor advisory
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 12:56 UTCVendor advisory
  37. 2026-08-09 08:59 UTCVendor advisory
  38. 2026-08-09 05:02 UTCVendor advisory
  39. 2026-08-08 11:23 UTCVendor advisory
  40. 2026-08-08 06:54 UTCVendor advisory
  41. 2026-08-08 02:57 UTCVendor advisory
  42. 2026-08-07 23:00 UTCVendor advisory
  43. 2026-08-07 19:03 UTCEG score recompute
  44. 2026-08-07 19:03 UTCVendor advisory
  45. 2026-08-07 15:06 UTCVendor advisory
  46. 2026-08-06 17:39 UTCEG score recompute
  47. 2026-08-06 17:39 UTCVendor advisory
  48. 2026-08-06 13:46 UTCEPSS rescore
  49. 2026-08-06 13:02 UTCVendor advisory
  50. 2026-08-06 08:24 UTCVendor advisory
  51. 2026-08-06 04:04 UTCVendor advisory
  52. 2026-08-06 00:07 UTCEG score recompute
  53. 2026-08-06 00:07 UTCVendor advisory
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:38 UTCEPSS rescore
  57. 2026-08-04 02:25 UTCVendor advisory
  58. 2026-08-03 22:28 UTCEG score recompute
  59. 2026-08-03 22:28 UTCVendor advisory
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 02:22 UTCVendor advisory
  62. 2026-08-02 22:25 UTCVendor advisory
  63. 2026-08-02 18:27 UTCVendor advisory
  64. 2026-08-02 14:24 UTCEG score recompute
  65. 2026-08-02 14:24 UTCVendor advisory
  66. 2026-08-02 02:27 UTCEPSS rescore
  67. 2026-08-01 04:16 UTCEPSS rescore
  68. 2026-07-30 16:28 UTCEPSS rescore
  69. 2026-07-30 01:30 UTCEPSS rescore
  70. 2026-07-27 14:13 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-25 14:18 UTCEPSS rescore
  75. 2026-07-24 14:17 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-35030?
CVE-2026-35030 is a critical vulnerability published on April 6, 2026. LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, when JWT authentication is enabled (enablejwtauth: true), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20…
When was CVE-2026-35030 disclosed?
CVE-2026-35030 was first published in the National Vulnerability Database on April 6, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35030 actively exploited?
CVE-2026-35030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.3% of all scored CVEs.
What is the CVSS score of CVE-2026-35030?
CVE-2026-35030 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-35030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35030

Explore →

Is Your Infrastructure Affected by CVE-2026-35030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs