GHSA-5mg7-485q-xm76 json
Two LiteLLM versions published containing credential harvesting malware
published 7mo ago modified 7mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Is GHSA-5mg7-485q-xm76 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | litellm | >=1.82.7, <=1.82.8 |
no fix listed |
Classification
- Weakness
-
- CWE-506 Embedded Malicious Code
References
-
github.com
/BerriAI/litellm/issues/24518
web
-
docs.litellm.ai
/blog/security-update-march-2026
web
-
futuresearch.ai
/blog/litellm-pypi-supply-chain-attack
web
-
github.com
/BerriAI/litellm
package
-
github.com
/pypa/advisory-database/tree/main/vulns/litellm/PYSEC-2026-2.yaml
web
-
inspector.pypi.io
/project/litellm/1.82.7/packages/79/5f/b6998d42c6ccd32d36e12661f2734602e72a576d52a51f4245aef0b20b4d/litellm-1.
web
-
inspector.pypi.io
/project/litellm/1.82.8/packages/f6/2c/731b614e6cee0bca1e010a36fd381fba69ee836fe3cb6753ba23ef2b9601/litellm-1.
web
-
wiz.io
/blog/teampcp-attack-kics-github-action
web
Sources
- GitHub Advisory GHSA-5mg7-485q-xm76
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.