In 30 seconds
CISA has placed CVE-2026-40217, a flaw in BerriAI LiteLLM, on its Known Exploited Vulnerabilities catalog. The entry, dated November 18, 2026, warns that an unprotected alternate channel could let remote attackers execute arbitrary code, meaning run whatever commands they choose, through bytecode rewriting at the /guardrails/test_custom_code URI. The federal deadline to act is December 2, 2026.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
A KEV listing is widely read as CISA signaling that a flaw is under real world attack, and the calendar sharpens the message: agencies get two weeks between the November 18 entry and the December 2 deadline. Exposed LiteLLM deployments are urgent business.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
What happened
The catalog entry names the flaw precisely: an Unprotected Alternate Channel Vulnerability in BerriAI LiteLLM, tracked as CVE-2026-40217. According to the description, the attack path runs through bytecode rewriting at the /guardrails/test_custom_code URI and could allow remote attackers to execute arbitrary code.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
The listing comes with orders, not just information. CISA directs users to apply mitigations in accordance with vendor instructions, to comply with BOD 26-04 on prioritizing security updates based on risk, to follow the agency's Forensics Triage Requirements, and to evaluate each asset's internet exposure. Where mitigations are unavailable, the guidance says to follow the applicable BOD 26-04 guidance for cloud services or discontinue use of the product.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Why it matters
Remote code execution sits at the ceiling of severity for web flaws: an outsider who can run arbitrary code on a server effectively controls it. The entry describes the trigger as a URI, an address an attacker can simply send a request to, which makes this kind of bug cheap to hunt at internet scale.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
The obligation travels beyond government. BOD 26-04 binds federal agencies to the catalog's deadlines, and many private security teams mirror KEV in their own patch priorities, so one entry can reset schedules across many networks at once.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
What to do
The entry's instructions are concrete. Apply mitigations in accordance with vendor instructions, with CISA's BOD 26-04 risk guidance and Forensics Triage Requirements in hand, and check whether your instance is exposed to the internet in the first place.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Running the product as a cloud service does not exempt you: follow the applicable BOD 26-04 guidance for cloud services, and if no mitigation exists, discontinue use of the product. For federal agencies the clock stops on December 2, 2026.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Confirmed and still uncertain
Established by the entry: the affected product, the vulnerability type, the code execution path via bytecode rewriting at the /guardrails/test_custom_code URI, the required action, and the December 2, 2026 federal deadline.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Left open by the entry: it lists ransomware use of the flaw as Unknown, and it names no victims, no sectors, and no affected versions.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Who is exploiting the flaw, and how broadly, remains unstated. This batch offers only the catalog entry, so those questions stay open until vendor advisories or incident reports surface.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
What people are saying
The only speaker in this batch is CISA, and it speaks through required action text. Its directives are blunt: apply mitigations in accordance with vendor instructions, ensure compliance with BOD 26-04, follow the Forensics Triage Requirements, and remember that stakeholders are responsible for evaluating each asset's internet exposure.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
BerriAI, security researchers, and any victims have not yet appeared in the evidence. Their accounts, especially on patch availability and real incidents, would be the natural next voices in this story.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Evolution
The paper trail in this batch begins and ends with the November 18, 2026 catalog entry. In a single move, CVE-2026-40217 acquired a public name, an attack description, a required action, and a hard deadline two weeks later, on December 2, 2026.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Everything before the listing stays dark here: when the flaw was found, when or whether a fix shipped, and whether attackers were inside before the public knew. The likely next beats are vendor advisory details, detections in the wild, and any incident reports tied to the URI.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Reach
1 independent groups, 1 updates, and 0 engagements.
Technical detail
In the catalog's words, the flaw is an unprotected alternate channel vulnerability in BerriAI LiteLLM that could allow remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI. The entry lists ransomware use as Unknown.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Translated: an alternate channel is a second route into the software that bypasses the checks guarding the front door, and bytecode rewriting means attacker supplied code is converted into the low level instructions the machine actually runs. If the channel executes that result, the attacker's code becomes the server's code.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Sources and evidence
This item rests on a single primary source: the KEV catalog entry for CVE-2026-40217, published November 18, 2026 and referenced at its NVD record page, which supplies the vulnerability description, the required action, and the federal deadline.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list
Missing from the batch: the vendor's own advisory, exploit samples or telemetry, and any victim reporting. The exploitation signal is therefore institutional, CISA's decision to list the flaw, rather than independent technical evidence in hand.CVE-2026-40217: BerriAI LiteLLM (BerriAI LiteLLM Unprotected Alternate Channel Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list



