CVE-2026-12796

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-06-21. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.6%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was identified in BerriAI litellm up to 1.82.2." No release containing a fix is confirmed on record.

A vulnerability was identified in BerriAI litellm up to 1.82.2. This impacts the function get_redirect_response_from_openid of the file litellm/proxy/management_endpoints/ui_sso.py of the component SSO Authentication Flow. The manipulation leads to session expiration. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

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 (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

June 21, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Jun 21, 2026
No fix on record yet.
Web page

SSO Login Does Not Invalidate Previous UI Session Tokens — Token Accumulation Leads to Persistent Unauthorized Access · GitHub

https://gist.github.com/YLChen-007/5fa8af12e1b183674d7ca96d852fb697

Vendor Advisories for CVE-2026-12796(1)

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
piplitellm—ghsa

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 rangeFix by version rangeDependents
litellm0.1.0 ... 1.9.dev0 (723 versions)
  • every version through 1.82.2: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 26× 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.

Showing the most recent 100 of 190 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-12796?
CVE-2026-12796 is a medium-severity vulnerability; its CVE record was published on June 21, 2026. A vulnerability was identified in BerriAI litellm up to 1.82.2. This impacts the function getredirectresponsefromopenid of the file litellm/proxy/managementendpoints/uisso.py of the component SSO Authentication Flow. The manipulation leads to session expiration. The attack is possible to be carried…
When was the CVE record for CVE-2026-12796 published?
The CVE record for CVE-2026-12796 was published on June 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 24, 2026; the record at its source may have been updated since.
Is CVE-2026-12796 actively exploited?
CVE-2026-12796 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12796?
CVE-2026-12796 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12796?
No fix for CVE-2026-12796 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A vulnerability was identified in BerriAI litellm up to 1.82.2." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-12796 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12796?

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