CVSS 4.0
9.5 criticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCritical (9.5) in litellm litellm. EPSS 3.0% estimated probability of exploitation activity in the next 30 days. Fixed in litellm 1.84.0.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hlitellm (PyPI): fixed in 1.84.0Explain CVE-2026-49468 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49468?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49468?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49468 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| litellm:litellm | before 1.84.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-4xpc-pv4p-pm3w | PyPI | litellm | <1.84.0 | 1.84.0 |
| PYSEC-2026-388 | PyPI | litellm | <1.84.0 | 1.84.0 |
Red Hat rates this Important.
The vulnerability is rated with Important severity due to the limited attack surface in our default deployment configuration.
While the affected images ship with a vulnerable version of litellm, the specific vulnerability is restricted solely to proxy management-route authentication. By default, these images do not start the LiteLLM proxy server. Instead, the default entrypoints are configured to run OGX, the MLflow server (with the AI Gateway disabled), Garak evaluation jobs, or Lightspeed/Llama Stack APIs. The proxy auth bypass is not reachable unless an administrator separately deploys litellm --config from the container.
For Red Hat OpenShift AI and Ansible Automation Platform products, the severity has been set to low since these products include litellm as a dependency in some images but do not run the LiteLLM proxy in default configurations, hence the vulnerable code path is not exposed.
To mitigate the risk of unauthenticated access, restrict network access to the LiteLLM proxy's management routes. Configure network firewalls or security groups to permit inbound connections only from trusted internal networks. This operational control limits the exposure of vulnerable endpoints to unauthorized external access. If the LiteLLM proxy is deployed behind a load balancer or API gateway, ensure these components are configured to strictly validate and sanitize the HTTP Host header before forwarding requests.
| Product | Package | State | Advisory |
|---|---|---|---|
| Exploit Intelligence | exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 | Affected | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-26/lightspeed-chatbot-rhel9 | Fix deferred | |
| Red Hat Ansible Automation Platform 2 | ansible-automation-platform-27/lightspeed-chatbot-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-llama-stack-core-rhel9 | Fix deferred | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-mlflow-rhel9 | Affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-49468.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.