Two LiteLLM versions published containing credential harvesting malware
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI litellm
- Affected
- >= 1.82.7, <= 1.82.8
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5mg7-485q-xm76 lists affected ranges: PyPI litellm >=1.82.7 <=1.82.8
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-5mg7-485q-xm76 lists affected ranges: PyPI litellm >=1.82.7 <=1.82.8
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
After an API Token exposure from an exploited trivy dependency, two new releases of litellm were uploaded to PyPI containing automatically activated malware, harvesting sensitive credentials and files, and exfiltrating to a remote API. Anyone who has installed and run the project should assume any credentials available to litellm environment may have been exposed, and revoke/rotate thema ccordingly.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-5mg7-485q-xm76
- Revision 2 · amended ·
Amended from osv record GHSA-5mg7-485q-xm76
- Revision 1 · created ·
Published from ghsa record GHSA-5mg7-485q-xm76
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-5mg7-485q-xm76 Advisory: Two LiteLLM versions published containing credential harvesting malware IDs: GHSA-5mg7-485q-xm76 Record: https://patchnext.com/advisories/ghsa-5mg7-485q-xm76 (revision 3, source checked 26 Oct 2026, 13:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI litellm: affected >= 1.82.7, <= 1.82.8 ## Suggested inspection (read-only) - `python -m pip show litellm`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on litellm. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-5mg7-485q-xm76 (GitHub-reviewed advisory GHSA-5mg7-485q-xm76 lists affected ranges: PyPI litellm >=1.82.7 <=1.82.8) - Verified: https://osv.dev/vulnerability/GHSA-5mg7-485q-xm76 (OSV record GHSA-5mg7-485q-xm76 lists affected ranges: PyPI litellm >=1.82.7 <=1.82.8) Commands are suggestions: review each one before running it.
Loading voting…