How many CVEs have patched _sanitize_for_log?

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

What is the latest CVE that changed _sanitize_for_log?

CVE-2026-59823 (LiteLLM: Server-side request forgery via the `user_config` request parameter in LiteLLM Proxy), published 2026-09-16, changed lines 46 to 47 of litellm/proxy/litellm_pre_call_utils.py.

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

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

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

Log in Create an account

BerriAI/litellm

Function

_sanitize_for_log

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

litellm/proxy/litellm_pre_call_utils.py

Last patched September 16, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

2

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_sanitize_for_log in BerriAI/litellm was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 2 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 _sanitize_for_log, newest first, with the lines each fix touched.

LiteLLM: Server-side request forgery via the `user_config` request parameter in LiteLLM Proxy
CVE-2026-59823 · lines 46–47 · +2 −0
Medium · CVSS 5.3
EPSS 0.4%2026-09-16

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.

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 _sanitize_for_log.

How many CVEs have patched _sanitize_for_log?: 1 published CVEs changed _sanitize_for_log in BerriAI/litellm, in 2 distinct patches totalling 2 changed lines, between 2026 and 2026.
What is the latest CVE that changed _sanitize_for_log?: CVE-2026-59823 (LiteLLM: Server-side request forgery via the `user_config` request parameter in LiteLLM Proxy), published 2026-09-16, changed lines 46 to 47 of litellm/proxy/litellm_pre_call_utils.py.
How does _sanitize_for_log compare to the rest of BerriAI/litellm?: BerriAI/litellm has 22 CVEs with a located fix in total; 1 of them changed _sanitize_for_log.
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

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