How many CVEs have patched get_provider_specific_params?

1 published CVEs changed get_provider_specific_params in BerriAI/litellm, in 1 distinct patches totalling 6 changed lines, between 2026 and 2026.

What is the latest CVE that changed get_provider_specific_params?

CVE-2026-59821 (LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks), published 2026-07-08, changed lines 1347 to 1349 of litellm/proxy/guardrails/guardrail_endpoints.py.

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

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

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
Get_provider_specific_params

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
Get_provider_specific_params

get_provider_specific_params in BerriAI/litellm: Patched by 1 CVEs

BerriAI/litellm

Function

get_provider_specific_params

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

litellm/proxy/guardrails/guardrail_endpoints.py

Last patched July 8, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

get_provider_specific_params in BerriAI/litellm was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 6 lines in total.

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

CVEs that patched it

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

LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks
CVE-2026-59821 · lines 1347–1349 · +3 −3
Low · CVSS 2.1
EPSS 0.9%2026-07-08

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.

1apply_guardraillitellm/proxy/guardrails/guardrail_endpoints.py1 CVEs · 1 patches2026
2create_guardraillitellm/proxy/guardrails/guardrail_endpoints.py1 CVEs · 1 patches2026
3delete_guardraillitellm/proxy/guardrails/guardrail_endpoints.py1 CVEs · 1 patches2026
4patch_guardraillitellm/proxy/guardrails/guardrail_endpoints.py1 CVEs · 1 patches2026
5test_custom_code_guardraillitellm/proxy/guardrails/guardrail_endpoints.py1 CVEs · 1 patches2026
6update_guardraillitellm/proxy/guardrails/guardrail_endpoints.py1 CVEs · 1 patches2026

Other hotspots in the repository

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

_validate_update_key_data4 CVEs · litellm/proxy/management_endpoints/key_management_endpoints.py _common_key_generation_helper3 CVEs · litellm/proxy/management_endpoints/key_management_endpoints.py validate_key_list_check3 CVEs · litellm/proxy/management_endpoints/key_management_endpoints.py _rotate_master_key3 CVEs · litellm/proxy/management_endpoints/key_management_endpoints.py delete_verification_tokens3 CVEs · litellm/proxy/management_endpoints/key_management_endpoints.py _fetch_user_team_objects3 CVEs · litellm/proxy/management_endpoints/key_management_endpoints.py

All patched functions in BerriAI/litellm

Frequently asked questions

Common questions about CVE fixes to get_provider_specific_params.

How many CVEs have patched get_provider_specific_params?: 1 published CVEs changed get_provider_specific_params in BerriAI/litellm, in 1 distinct patches totalling 6 changed lines, between 2026 and 2026.
What is the latest CVE that changed get_provider_specific_params?: CVE-2026-59821 (LiteLLM: Custom Code Guardrails production endpoints bypass code safety checks), published 2026-07-08, changed lines 1347 to 1349 of litellm/proxy/guardrails/guardrail_endpoints.py.
How does get_provider_specific_params compare to the rest of BerriAI/litellm?: BerriAI/litellm has 22 CVEs with a located fix in total; 1 of them changed get_provider_specific_params.
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/guardrails/guardrail_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