# LiteLLM proxy guardrail flaw CVE-2026-40217 added to KEV

Canonical: https://www.oktsec.com/radar/litellm-custom-guardrail-cve-2026-40217
Publisher: Oktsec
Language: en
Published: 2026-11-18T21:03:37Z
Updated: 2026-11-18T21:03:37Z
Record reviewed: 2026-11-18T21:03:37Z
Latest evidence check: 2026-11-18T21:03:37Z
Disclosed: 2026-05-07

CISA confirms known exploitation of the custom guardrail sandbox flaw. BerriAI says an attacker who can reach the test function can run code with the privileges of the proxy process.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Act now
- Rationale: CISA added this exact CVE to KEV. BerriAI identifies administrator credentials as a prerequisite in the default configuration.
- Evidence: Attacks confirmed
- Verification: Multiple sources
- Fix status: Fix available
- Exposure requirement: Account access required
- Vendor: BerriAI
- Products: LiteLLM Proxy
- CVEs: CVE-2026-40217

## Technical overview

The advisory metadata lists 1.83.10 as patched, while the remediation text recommends 1.83.11 or later. Use the latter recommendation when verifying a deployment. The KEV record identifies the guardrail flaw and provides no victim count.

## Recommended response

Follow BerriAI’s recommendation to upgrade to 1.83.11 or later. If an upgrade must wait, block the custom code test endpoint at the reverse proxy or API gateway.

Relevant to: Identify deployments of LiteLLM Proxy and check their installed version and administrator access.

## CVE attribution

- CVE-2026-40217: BerriAI — LiteLLM Proxy. [Source](https://github.com/BerriAI/litellm/security/advisories/GHSA-wxxx-gvqv-xp7p)

## Affected systems and fixes

### LiteLLM Proxy

Affected: Custom guardrail testing on an affected proxy. Default configurations require a proxy administrator credential.

Fixed release / action: 1.83.11 or later, as recommended in the advisory text

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.18
Checked: 2026-11-18T21:06:31.057Z

### [CVE-2026-40217](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-40217)

- Added: 2026-11-18
- Ransomware use: Not confirmed by CISA
- Federal due date: 2026-12-02
- Federal forensic triage: No

Action specified by CISA: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-19T21:12:22.272Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-40217](https://api.first.org/data/v1/epss?cve=CVE-2026-40217): 61.91% probability of observed exploitation in the next 30 days; percentile 99.19%; score date 2026-11-19.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-19T21:12:22.272Z.

## Response checklist

1. **Locate the proxy** — Identify deployments of LiteLLM Proxy and check their installed version and administrator access.
2. **Restrict the test endpoint** — Apply the vendor workaround at the gateway if the proxy cannot be updated immediately.
3. **Review proxy access** — For exposed deployments, examine administrator activity and access to model provider credentials held by the proxy.

## Relevance to AI environments

For exposed deployments, examine administrator activity and access to model provider credentials held by the proxy.

## Sources

- [Custom guardrail advisory and workaround](https://github.com/BerriAI/litellm/security/advisories/GHSA-wxxx-gvqv-xp7p) — BerriAI; Vendor notice; checked 2026-11-18T21:03:37Z
- [Known Exploited Vulnerabilities catalog, November 18](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json) — CISA; Government advisory; checked 2026-11-18T21:03:37Z

## Editorial record

- 2026-11-18T21:03:37Z: Added the November 18 KEV listing and the applicable response.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/litellm-custom-guardrail-cve-2026-40217) · [Build a response plan](https://www.oktsec.com/radar/litellm-custom-guardrail-cve-2026-40217#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=litellm-custom-guardrail-cve-2026-40217&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=litellm-custom-guardrail-cve-2026-40217&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

