Loading vulnerability…
SQL Injection vulnerability in BerriAI LiteLLM before 1.81.0 allows attackers to execute arbitrary commands via the key parameter to the "/key/block" and "/key/unblock" API endpoints.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a standalone Python PoC for CVE-2025-45809, a time-based blind SQL injection in LiteLLM’s POST /key/block and /key/unblock endpoints when the JSON key parameter is interpolated into SQL queries without parameterization. The repo contains a runnable exploit (exploit/exploit.py), a payload construction helper (exploit/payload.py), Docker infrastructure to reproduce the issue against LiteLLM 1.65.4 with PostgreSQL, and documentation/advisory material. Main exploit capabilities: the script first verifies target reachability using GET /model/info or /, then sends crafted POST requests to /key/block (or optionally /key/unblock) with injected key values. It supports confirmation of the vulnerability using pg_sleep()-based timing, extraction of database values such as current_user or version() through conditional substring checks, custom query extraction, and attempted arbitrary file disclosure using PostgreSQL pg_read_file(). The exploit uses a hardcoded default API key (sk-litellm-master-key) matching the included lab configuration. Repository structure: exploit/exploit.py is the main entry point and CLI driver; exploit/payload.py builds SQLi payloads; docker-compose.yml provisions PostgreSQL plus vulnerable and fixed LiteLLM containers for side-by-side testing; litellm-vuln/Dockerfile pins LiteLLM[proxy]==1.65.4; litellm_config.yaml defines the master key and database URL; README.md and docs/advisory.md document the vulnerability, usage, and remediation. Overall, this is a real exploit PoC rather than a mere detector, because it includes active exfiltration and file-read logic beyond simple vulnerability checking.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.