
A guardrail’s test endpoint is still executable code. If an MSP or customer runs LiteLLM as an AI gateway, verify who can reach its custom-code route and what the proxy process can access.
What is new — November 18, 2026
CVE-2026-40217 / GHSA-wxxx-gvqv-xp7p is newly in CISA KEV. The vendor GitHub advisory was published May 7, 2026. This is new exploitation evidence for an older advisory, not a new product release.
CISA added this CVE to KEV on November 18, 2026, establishing known exploitation. Ransomware use is listed as Unknown. A KEV entry does not establish compromise of any customer system.
The vendor rates the issue Moderate, CVSS 4.0 5.9. Its default configuration requires a proxy-admin credential to reach POST /guardrails/test_custom_code. A bytecode-level sandbox escape permits arbitrary code in the proxy process, which the vendor says runs as root in its default Docker image. Do not describe this as an unauthenticated default-configuration attack.
Affected versions and conflicting fix guidance
The vendor matrix lists 1.81.8 ≤ version < 1.83.10 as affected and ≥1.83.10 as patched, linking v1.83.10-stable. The same advisory’s patch prose says fixed in 1.83.11 and explicitly recommends 1.83.11 or later. The contradiction is unresolved. Suggested rollout target: a supported 1.83.11-or-later build, verify its actual package and application behavior; do not close a 1.83.10 deployment solely from the conflicting matrix.
If immediate upgrading is impractical, the vendor directs blocking POST /guardrails/test_custom_code at the reverse proxy or API gateway. Verify the restriction on every route to the proxy; it is a temporary exposure control, not proof that the package is fixed. Review proxy-admin access and credential trust. No vendor-directed blanket credential rotation was verified; investigate and rotate affected secrets through incident response if evidence warrants it.
CISA lists a December 2, 2026 federal remediation deadline and forensicTriage: No. That flag does not mean an installation is clean or remove the need to investigate suspicious activity. The federal deadline is not Brian’s customer-specific obligation.
Suggested MSP priority and action
Urgent where an affected gateway is deployed and the endpoint is reachable. Inventory package/image and proxy-admin access → apply the vendor’s route block where a fix is pending and restrict unnecessary management access → stage a supported build meeting the conservative 1.83.11-or-later target → verify package, route enforcement, expected guardrail behavior and normal model traffic. Check the gateway’s integrations and process privileges; do not assume credentials were stolen.
Official evidence
Vendor advisory and version contradiction · CISA official KEV data
Last verified November 18, 2026 ET. No customer deployment or compromise is assumed. This scoped KEV check is not a comprehensive LiteLLM security baseline.