Proxy administration via unguarded M2M JWT routes
Published Jun 21, 2026 · Updated Jun 21, 2026
Improper authorization in BerriAI LiteLLM 1.82.0 through 1.82.2 allows remote authenticated users to gain proxy administration. The JWT M2M path in user_api_key_auth.py omits the route guard used by OAuth2 and returns the PROXY_ADMIN role for management endpoints. Exploitation requires LiteLLM Enterprise with JWT authentication enabled and a valid M2M JWT carrying the configured administrative scope; it permits user, team, and API-key management.
Summary
What happened
Improper authorization in BerriAI LiteLLM 1.82.0 through 1.82.2 allows remote authenticated users to gain proxy administration. The JWT M2M path in user_api_key_auth.py omits the route guard used by OAuth2 and returns the PROXY_ADMIN role for management endpoints. Exploitation requires LiteLLM Enterprise with JWT authentication enabled and a valid M2M JWT carrying the configured administrative scope; it permits user, team, and API-key management.
The record
- CVE
- CVE-2026-12771
- Published
- Jun 21, 2026
- Updated
- Jun 21, 2026
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-266, CWE-285, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2026CVE publishedPublication date reported by the CVE source.
- Jun 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.82.0
- Affected versionversion=1.82.1
- Affected versionversion=1.82.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- M2M JWT UI route-separation bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo