AAK-LITELLM-CVE-2026-30623-PIN-001: LiteLLM pin floor for CVE-2026-30623 (below 1.83.7)
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/supply_chain.py- Auto-fixable
- Yes.
agent-audit-kit fixcan apply it. - SARIF name
LitellmCveStaleVersion
What it detects
A Python manifest (requirements*.txt, pyproject.toml, Pipfile*, poetry.lock, uv.lock) pins litellm at a version below 1.83.7. BerriAI/litellm shipped the CVE-2026-30623 fix in v1.83.7 on 2026-04-30. AAK-MCP-STDIO-CMD-INJ-001 already covers the source-side architectural shape; this pin-only rule complements it by surfacing a discrete finding for consumers who run pin-check mode and need an actionable manifest fix. The <1.83.7 floor also flags the LiteLLM MCP-proxy CVE cluster, all in versions below the floor: CVE-2026-12773 (improper authentication in the MCP proxy UserAPIKeyAuth, <=1.59.8), CVE-2026-12774 (SSRF in MCP server connection testing, <=1.82.2), and CVE-2026-12798 (SSRF in the MCP OpenAPI spec loader, <=1.82.2). Wired into aak fix --cve so the auto-fixer can rewrite requirements*.txt entries to litellm>=1.83.7.
How to fix
Bump litellm to >= 1.83.7. aak fix --cve rewrites a requirements*.txt pin in place; pyproject.toml / lockfile edits should go through the project's normal dependency-update workflow.
agent-audit-kit fix can apply this change for you; add --dry-run to preview it.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-LITELLM-CVE-2026-30623-PIN-001
Limitations
Reads the dependency declarations of the root requirements*.txt, pyproject.toml and Pipfile in their own formats, and reports one whose range admits a release below 1.83.7 (litellm<1.83.7 included), and the version the root Pipfile.lock, poetry.lock or uv.lock resolves when it is below 1.83.7. A git requirement's dotted release tag is read as its version (@v1.83.0); a commit, a branch or a tag with no dot (@v2) states none. Only a tag written after the @ alone is read: @refs/tags/v1.83.0, and the release an archive's file name states (.../archive/refs/tags/v1.83.0.tar.gz, litellm-1.83.0.tar.gz), are not, so such a requirement states no version and is not reported, even below 1.83.7, though AAK-MCP-LITELLM-CVE-2026-59822-001 reads both forms. A declaration that states no version, such as litellm alone or a git URL without a release tag, is not reported, and neither is a requirements file in a sub-directory or an .mcp.json launcher. A compose file's ghcr.io/berriai/litellm image tag is not read. A manifest over 2 MB is not read. A lockfile over 32 MiB is not read.
References
- CVE: CVE-2026-30623, CVE-2026-12773, CVE-2026-12774, CVE-2026-12798
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP05:2025 (Command Injection & Execution)
- OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution (RCE))
- Incidents and advisories: BERRIAI-LITELLM-2026-04-30
- CSA AI Controls Matrix (AICM): STA-08, AIS-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-LITELLM-CVE-2026-30623-PIN-001.md: the page then shows that text, with the registry reference appended under it.