How many CVEs have patched delete_verification_tokens?

3 published CVEs changed delete_verification_tokens in BerriAI/litellm, in 3 distinct patches totalling 24 changed lines, between 2026 and 2026.

What is the latest CVE that changed delete_verification_tokens?

CVE-2026-37004 (LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint), published 2026-08-27, changed lines 3275 to 3278 of litellm/proxy/management_endpoints/key_management_endpoints.py.

How does delete_verification_tokens compare to the rest of BerriAI/litellm?

BerriAI/litellm has 22 CVEs with a located fix in total; 3 of them changed delete_verification_tokens.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Berriai
Litellm
Delete_verification_tokens

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Berriai
Litellm
Delete_verification_tokens

delete_verification_tokens in BerriAI/litellm: Patched by 3 CVEs

BerriAI/litellm

Function

delete_verification_tokens

Name: delete_verification_tokens in BerriAI/litellm: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

litellm/proxy/management_endpoints/key_management_endpoints.py

Last patched August 27, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

delete_verification_tokens in BerriAI/litellm was changed by 3 published CVE fixes in 2026, in 3 distinct patches that added or removed 24 lines in total.

BerriAI/litellm has 22 CVEs with a located fix in total, so 14% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed delete_verification_tokens, newest first, with the lines each fix touched.

LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint
CVE-2026-37004 · lines 3275–3278 · +4 −4
Critical · CVSS 9.8
EPSS 0.8%2026-08-27
LiteLLM < 1.83.10 Privilege Escalation via User Update
CVE-2026-47102 · lines 3280–3283 · +4 −4
High · CVSS 8.7
EPSS 0.8%2026-05-21
LiteLLM < 1.83.14 Privilege Escalation via API Key Generation
CVE-2026-47101 · lines 3275–3278 · +4 −4
High · CVSS 8.7
EPSS 1.3%2026-05-21

Get an alert when the next CVE fix lands in BerriAI/litellm, with the patched functions.

Monitor litellm CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1_validate_update_key_datalitellm/proxy/management_endpoints/key_management_endpoints.py4 CVEs · 5 patches2026
2_common_key_generation_helperlitellm/proxy/management_endpoints/key_management_endpoints.py3 CVEs · 5 patches2026
3_fetch_user_team_objectslitellm/proxy/management_endpoints/key_management_endpoints.py3 CVEs · 3 patches2026
4validate_key_list_checklitellm/proxy/management_endpoints/key_management_endpoints.py3 CVEs · 3 patches2026
5_rotate_master_keylitellm/proxy/management_endpoints/key_management_endpoints.py3 CVEs · 3 patches2026
6generate_key_fnlitellm/proxy/management_endpoints/key_management_endpoints.py2 CVEs · 2 patches2026
7_check_allowed_routes_caller_permissionlitellm/proxy/management_endpoints/key_management_endpoints.py2 CVEs · 1 patches2026
8regenerate_key_fnlitellm/proxy/management_endpoints/key_management_endpoints.py1 CVEs · 2 patches2026

Other hotspots in the repository

Functions in BerriAI/litellm changed by the most CVE fixes.

All patched functions in BerriAI/litellm

Frequently asked questions

Common questions about CVE fixes to delete_verification_tokens.

How many CVEs have patched delete_verification_tokens?: 3 published CVEs changed delete_verification_tokens in BerriAI/litellm, in 3 distinct patches totalling 24 changed lines, between 2026 and 2026.
What is the latest CVE that changed delete_verification_tokens?: CVE-2026-37004 (LiteLLM vulnerable to server-side template injection in the /prompts/test endpoint), published 2026-08-27, changed lines 3275 to 3278 of litellm/proxy/management_endpoints/key_management_endpoints.py.
How does delete_verification_tokens compare to the rest of BerriAI/litellm?: BerriAI/litellm has 22 CVEs with a located fix in total; 3 of them changed delete_verification_tokens.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

litellm/proxy/management_endpoints/key_management_endpoints.py on GitHub (opens in a new tab)
All patched functions in BerriAI/litellm
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track BerriAI/litellm CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References