How severe is GHSA-5mg7-485q-xm76?

No CVSS score has been assigned to GHSA-5mg7-485q-xm76 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5mg7-485q-xm76?

GHSA-5mg7-485q-xm76 affects the following packages: litellm (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-5mg7-485q-xm76?

The records we use list no patched version of litellm for GHSA-5mg7-485q-xm76. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-5mg7-485q-xm76 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for litellm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-5mg7-485q-xm76 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-5mg7-485q-xm76 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5mg7-485q-xm76 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5mg7-485q-xm76 published, and has it been updated?

GHSA-5mg7-485q-xm76 was published on March 25, 2026 and was last updated on March 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Two LiteLLM versions published containing credential harvesting malwareGHSA-5mg7-485q-xm76

GHSA-5mg7-485q-xm76 is a security vulnerability in litellm. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Mar 25, 2026

Updated

Mar 27, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Mar 27, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍litellm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`litellm`	≥ 1.82.7	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for litellm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of litellm for GHSA-5mg7-485q-xm76. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-5mg7-485q-xm76 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works