CVE-2026-12771

HIGHNVD 7.55.0▼
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory (severity: LOW) published 2026-06-21. NVD baseline CVSS 7.5; sources differ by 2.5.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
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
5.0(medium)
EPSS
20.6%
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 21× in last 7d / 51× 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-07 01:17 UTCEG score recompute
  2. 2026-07-07 01:17 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 01:28 UTCEG score recompute
  6. 2026-07-06 01:28 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-05 01:39 UTCEG score recompute
  10. 2026-07-05 01:39 UTCGHSA enrichment
  11. 2026-07-04 01:42 UTCEG score recompute
  12. 2026-07-04 01:42 UTCGHSA enrichment
  13. 2026-07-03 01:45 UTCEG score recompute
  14. 2026-07-03 01:44 UTCGHSA enrichment
  15. 2026-07-02 01:56 UTCEG score recompute
  16. 2026-07-02 01:55 UTCGHSA enrichment
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 02:07 UTCEG score recompute
  20. 2026-07-01 02:07 UTCGHSA enrichment
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 02:18 UTCEG score recompute
  23. 2026-06-30 02:18 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 02:30 UTCEG score recompute
Show 26 more
  1. 2026-06-29 02:29 UTCGHSA enrichment
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 02:40 UTCEG score recompute
  6. 2026-06-28 02:40 UTCGHSA enrichment
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-27 02:51 UTCEG score recompute
  9. 2026-06-27 02:50 UTCGHSA enrichment
  10. 2026-06-26 03:00 UTCEG score recompute
  11. 2026-06-26 03:00 UTCGHSA enrichment
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-25 03:11 UTCEG score recompute
  14. 2026-06-25 03:11 UTCGHSA enrichment
  15. 2026-06-24 22:03 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-24 03:23 UTCEG score recompute
  18. 2026-06-24 03:23 UTCGHSA enrichment
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-23 03:33 UTCEG score recompute
  21. 2026-06-23 03:33 UTCGHSA enrichment
  22. 2026-06-22 17:45 UTCNVD updateCVSS v4 → 1.3 · severity → MEDIUM
  23. 2026-06-22 03:39 UTCEG score recompute
  24. 2026-06-22 03:39 UTCGHSA enrichment
  25. 2026-06-21 03:49 UTCEG score recompute
  26. 2026-06-21 03:49 UTCGHSA enrichment

Related CVEs(same CWE)

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.6% 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). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.0.
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