CVE-2026-49468

Home/CVE/LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, This vulnerabili

CVE

↯ PDF report

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, This vulnerabili

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, This vulnerability is fixed in 1.84.0.

Monitor

⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)

No Sigma yet — build one → YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2026-49468, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

◆

ATT&CK techniques

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1036.001 · Invalid Code Signature T1134 · Access Token Manipulation T1134.001 · Token Impersonation/Theft T1528 · Steal Application Access Token T1539 · Steal Web Session Cookie T1550.004 · Web Session Cookie T1553.002 · Code Signing T1557 · Adversary-in-the-Middle

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-21 · Exploitation of Trusted Identifiers CAPEC-CAPEC-22 · Exploiting Trust in Client CAPEC-CAPEC-459 · Creating a Rogue Certification Authority Certificate CAPEC-CAPEC-461 · Web Services API Signature Forgery Leveraging Hash Function Extension Weakness CAPEC-CAPEC-473 · Signature Spoof CAPEC-CAPEC-476 · Signature Spoofing by Misrepresentation CAPEC-CAPEC-59 · Session Credential Falsification through Prediction CAPEC-CAPEC-60 · Reusing Session IDs (aka Session Replay) CAPEC-CAPEC-667 · Bluetooth Impersonation AttackS (BIAS) CAPEC-CAPEC-94 · Adversary in the Middle (AiTM)

⬡

Weakness Classification

CWE-290Authentication Bypass by Spoofing

▤

Affected Packages

Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.

PyPI litellm CRITICAL fixed in 1.84.0

▤

Related CVEs

CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.

CVE-1999-0012 Some web servers under Microsoft Windows allow remote attackers to bypass access... same CWE-290 HIGH CVE-2009-1048 The web interface on the snom VoIP phones snom 300, snom 320, snom 360, snom 370... same CWE-290 CRITICAL CVE-2013-5661 Cache Poisoning issue exists in DNS Response Rate Limiting. same CWE-290 MEDIUM CVE-2017-6405 An issue was discovered in Veritas NetBackup 8.0 and earlier and NetBackup Appli... same CWE-290 HIGH

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://github.com/BerriAI/litellm/releases/tag/v1.84.0

https://github.com/BerriAI/litellm/security/advisories/GHSA-4xpc-pv4p-pm3w