CVE-2026-12771

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

A vulnerability was identified in BerriAI litellm up to 1.82.2. This affects an unknown function of the file litellm/proxy/auth/user_api_key_auth.py of the component M2M JWT Handler. Such manipulation leads to improper authorization. The attack can be launched remotely. A high complexity level is associated with this attack. The exploitability is reported as difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
20.9%
KEV
Not listed

Published

June 21, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
No patch confirmed yet.
generic

M2M JWT Authentication Bypasses UI SSO Route Separation — Full Management Access via API Token · GitHub

https://gist.github.com/YLChen-007/70e4e106527f74ddf17953ff0f6c248d

Vendor Advisories for CVE-2026-12771(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute▲ 2.50
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 23:51 UTCGHSA enrichment
  10. 2026-07-16 17:02 UTCEPSS rescore
  11. 2026-07-16 00:03 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-15 00:13 UTCGHSA enrichment
  15. 2026-07-14 00:14 UTCGHSA enrichment
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 06:12 UTCEPSS rescore
  18. 2026-07-13 00:25 UTCGHSA enrichment
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-12 00:36 UTCGHSA enrichment
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-11 00:47 UTCGHSA enrichment
  23. 2026-07-10 00:59 UTCGHSA enrichment
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 00:54 UTCGHSA enrichment
Show 39 more
  1. 2026-07-08 15:15 UTCEPSS rescore
  2. 2026-07-08 15:15 UTCEPSS rescore
  3. 2026-07-08 01:05 UTCGHSA enrichment
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-07 01:17 UTCGHSA enrichment
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 01:28 UTCGHSA enrichment
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 01:39 UTCGHSA enrichment
  12. 2026-07-04 01:42 UTCGHSA enrichment
  13. 2026-07-03 01:44 UTCGHSA enrichment
  14. 2026-07-02 01:55 UTCGHSA enrichment
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 02:07 UTCGHSA enrichment
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 02:18 UTCGHSA enrichment
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 02:29 UTCGHSA enrichment
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 02:40 UTCGHSA enrichment
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-27 02:50 UTCGHSA enrichment
  28. 2026-06-26 03:00 UTCGHSA enrichment
  29. 2026-06-25 13:49 UTCEPSS rescore
  30. 2026-06-25 03:11 UTCGHSA enrichment
  31. 2026-06-24 22:03 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  32. 2026-06-24 14:05 UTCEPSS rescore
  33. 2026-06-24 03:23 UTCGHSA enrichment
  34. 2026-06-23 21:32 UTCEPSS rescore
  35. 2026-06-23 03:33 UTCGHSA enrichment
  36. 2026-06-22 17:45 UTCNVD updateCVSS v4 → 1.3 · severity → MEDIUM
  37. 2026-06-22 03:39 UTCGHSA enrichment
  38. 2026-06-21 03:49 UTCEG score recompute
  39. 2026-06-21 03:49 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-12771?
CVE-2026-12771 is a high vulnerability published on June 21, 2026. A vulnerability was identified in BerriAI litellm up to 1.82.2. This affects an unknown function of the file litellm/proxy/auth/userapikey_auth.py of the component M2M JWT Handler. Such manipulation leads to improper authorization. The attack can be launched remotely. A high complexity level is…
When was CVE-2026-12771 disclosed?
CVE-2026-12771 was first published in the National Vulnerability Database on June 21, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12771 actively exploited?
CVE-2026-12771 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12771?
CVE-2026-12771 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-12771?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12771, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-12771?

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

Start Free Scan →Browse All CVEs