CVE-2026-93355

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. The CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-88462 (ENISA EUVD) · GHSA-g83g-3c4g-cfm5 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

LiteLLM contains a weak authentication vulnerability that allows an attacker holding a valid JWT from the configured identity provider to authenticate as any existing user by exploiting an email-based fallback lookup in the JWT authentication flow without verifying the email_verified claim. Attackers can present a token with an unverified email address matching a victim's account to inherit the victim's role, including proxy_admin privileges, and permanently overwrite the victim's stored identity binding to retain persistent unauthorized access to administrative endpoints exposing API keys and user management.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 28, 2026

Last Modified

October 1, 2026

Advisory Details (2)

Auto-updated Sep 28, 2026
Patch available.
Web page

LiteLLM Weak JWT Authentication via Email-Based User Lookup | Advisories | VulnCheck

https://www.vulncheck.com/advisories/litellm-weak-jwt-authentication-via-email-based-user-lookup
Web page

LiteLLM: an ordinary login token can become someone else’s admin account | OX Security

https://www.ox.security/blog/litellm-an-ordinary-login-token-can-become-someone-elses-admin-account/

Vendor Advisories for CVE-2026-93355(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-trustyai-garak-lls-provider-dsp-rhel9:17917858042026-10-19redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 70× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-28 21:32 UTCEG score recompute
  7. 2026-10-28 21:32 UTCVendor advisory
  8. 2026-10-28 21:32 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-27 20:11 UTCEG score recompute
  11. 2026-10-27 20:11 UTCVendor advisory
  12. 2026-10-27 20:11 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-25 13:49 UTCEG score recompute
  17. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-20 06:55 UTCEG score recompute
  23. 2026-10-20 06:55 UTCVendor advisory
  24. 2026-10-20 06:55 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 71 more
  1. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-18 02:59 UTCEG score recompute
  3. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-13 04:27 UTCEG score recompute
  9. 2026-10-13 04:27 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-12 14:43 UTCEG score recompute
  12. 2026-10-11 19:12 UTCEG score recompute
  13. 2026-10-11 18:09 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-11 16:28 UTCEG score recompute
  15. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-11 13:42 UTCEG score recompute
  17. 2026-10-11 05:46 UTCEG score recompute
  18. 2026-10-11 05:46 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-10 17:45 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-10-10 05:43 UTCEG score recompute
  22. 2026-10-10 05:43 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-09 17:39 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-10-09 04:53 UTCEG score recompute
  26. 2026-10-09 04:53 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-10-08 16:51 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-10-08 04:29 UTCEG score recompute
  30. 2026-10-08 04:29 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-10-07 16:27 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-10-07 04:05 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-10-06 16:03 UTCEG score recompute
  35. 2026-10-06 16:03 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  36. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-10-06 04:01 UTCEG score recompute
  38. 2026-10-06 04:00 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  39. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-10-05 15:55 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-10-05 03:37 UTCEG score recompute
  42. 2026-10-05 03:37 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  43. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-10-04 15:36 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-10-04 03:34 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  46. 2026-10-03 15:33 UTCEG score recompute
  47. 2026-10-03 15:33 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  48. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-10-03 03:31 UTCEG score recompute
  50. 2026-10-03 03:31 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  51. 2026-10-02 15:29 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  52. 2026-10-02 03:27 UTCEG score recompute
  53. 2026-10-02 03:27 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-10-01 15:26 UTCEG score recompute
  56. 2026-10-01 15:26 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-10-01 05:27 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  58. 2026-09-30 17:26 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-09-30 16:16 UTCEG score recompute
  60. 2026-09-30 16:16 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  62. 2026-09-30 03:28 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-09-29 15:25 UTCEG score recompute
  64. 2026-09-29 15:25 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-09-29 14:27 UTCEG score recompute
  66. 2026-09-29 14:26 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  67. 2026-09-29 08:31 UTCEG score recompute
  68. 2026-09-29 08:30 UTCGHSA enrichmentGHSA-g83g-3c4g-cfm5 · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-09-28 20:29 UTCEG score recompute
  70. 2026-09-28 19:37 UTCEG score recomputeFirst assessed: 8.1 HIGH
  71. 2026-09-28 19:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93355?
CVE-2026-93355 is a high-severity vulnerability; its CVE record was published on September 28, 2026. LiteLLM contains a weak authentication vulnerability that allows an attacker holding a valid JWT from the configured identity provider to authenticate as any existing user by exploiting an email-based fallback lookup in the JWT authentication flow without verifying the email_verified claim.…
When was CVE-2026-93355 made public?
CVE-2026-93355 was made public on September 28, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 28, 2026. EchelonGraph's copy of the record carries a last-modified date of October 1, 2026; the record at its source may have been updated since.
Is CVE-2026-93355 actively exploited?
CVE-2026-93355 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93355?
CVE-2026-93355 has a CVSS base score of 8.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-93355?
A fix for CVE-2026-93355 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-93355 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93355

Explore →

Is Your Infrastructure Affected by CVE-2026-93355?

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