BerriAI litellm up to 1.82.2 M2M JWT user_api_key_auth.py improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 1.21 |
Summary
A vulnerability, which was classified as critical, has been found in BerriAI litellm up to 1.82.2. This impacts an unknown function of the file litellm/proxy/auth/user_api_key_auth.py of the component M2M JWT Handler. Performing a manipulation results in improper authorization. This vulnerability was named CVE-2026-12771. The attack may be initiated remotely. In addition, an exploit is available. The vendor was contacted early about this disclosure.
Details
A vulnerability, which was classified as critical, was found in BerriAI litellm up to 1.82.2. This affects an unknown functionality of the file litellm/proxy/auth/user_api_key_auth.py of the component M2M JWT Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at gist.github.com. This vulnerability is uniquely identified as CVE-2026-12771. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.0
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/20/2026 Advisory disclosed06/20/2026 VulDB entry created
06/20/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-12771 (🔒)
GCVE (CVE): GCVE-0-2026-12771
GCVE (VulDB): GCVE-100-372513
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/20/2026 11:31Changes: 06/20/2026 11:31 (56)
Complete: 🔍
Submitter: Eric-c
Cache ID: 216::103
Submit
Accepted
- Submit #811280: litellm <= 1.82.2 Improper Authorization (CWE-285) (by Eric-c)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.