CVE-2026-12795

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

Score 7.3 from GitHub Security Advisory published 2026-06-21. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
7.3EG
EchelonGraph verdictPlan mitigationRemediate 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.8%CVSS: 7.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 determined in BerriAI litellm up to 1.82.2." No release containing a fix is confirmed on record.

A vulnerability was determined in BerriAI litellm up to 1.82.2. This affects the function json.dumps of the file litellm/proxy/management_endpoints/ui_sso.py of the component SSO Debug Flow. Executing a manipulation can lead to missing authentication. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
64
EG Risk 64/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)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 22, 2026
No fix on record yet.
Web page

Unauthenticated SSO Debug Endpoints Expose User Data and Enable Potential XSS via Unsafe HTML Injection · GitHub

https://gist.github.com/YLChen-007/9b13c75a3a73187a4082cc6df0b100d3

Vendor Advisories for CVE-2026-12795(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(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 25× 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 254 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 154 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-12795?
CVE-2026-12795 is a high-severity vulnerability; its CVE record was published on June 21, 2026. A vulnerability was determined in BerriAI litellm up to 1.82.2. This affects the function json.dumps of the file litellm/proxy/managementendpoints/uisso.py of the component SSO Debug Flow. Executing a manipulation can lead to missing authentication. The attack can be executed remotely. The exploit…
When was the CVE record for CVE-2026-12795 published?
The CVE record for CVE-2026-12795 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-12795 actively exploited?
CVE-2026-12795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12795?
CVE-2026-12795 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12795?
No fix for CVE-2026-12795 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 determined 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-12795 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-12795

Explore →

Is Your Infrastructure Affected by CVE-2026-12795?

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

Book a Demo →Browse All CVEs