How severe is GHSA-xm4r-5rj9-2pg3?

GHSA-xm4r-5rj9-2pg3 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xm4r-5rj9-2pg3?

GHSA-xm4r-5rj9-2pg3 affects the following packages: gratient (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xm4r-5rj9-2pg3?

The records we use list no patched version of gratient for GHSA-xm4r-5rj9-2pg3. 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-xm4r-5rj9-2pg3 in my PyPI dependencies?

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

How do I mitigate GHSA-xm4r-5rj9-2pg3 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-xm4r-5rj9-2pg3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-xm4r-5rj9-2pg3 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-xm4r-5rj9-2pg3 published, and has it been updated?

GHSA-xm4r-5rj9-2pg3 was published on August 30, 2024. 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

HIGH severity

gratient 0.5 contains credential harvesting codeGHSA-xm4r-5rj9-2pg3

HIGH

GHSA-xm4r-5rj9-2pg3 is a high-severity (CVSS 7.5) vulnerability in gratient. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Aug 30, 2024

Updated

Aug 30, 2024

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 30, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍gratient

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

gratient is a user-facing library for generating color gradients of text. Version 0.5 contained obfuscated, malicious code targeting Windows platforms, harvesting information and credentials from the user's system and sending them to a remote server. Services may include Mullvad VPN and Telegram.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`gratient`	all versions	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 gratient, 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 gratient for GHSA-xm4r-5rj9-2pg3. 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

O3 Security · Impact-Aware SCA

Is GHSA-xm4r-5rj9-2pg3 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works