GHSA-65p8-3hm4-h9h8 — rgb2hex
MEDIUMGHSA-65p8-3hm4-h9h8 is a medium-severity (CVSS 6.5) vulnerability in rgb2hex. A fix is available for rgb2hex — see the affected versions and patch details below.
Denial of Service in rgb2hex
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
rgb2hexnpmDescription
All versions of rgb2hex are vulnerable to Regular Expression Denial of Service (ReDoS) when an attacker can pass in a specially crafted invalid color value.
Recommendation
Update to version 0.1.6 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | rgb2hex | all versions | 0.1.6npm install rgb2hex@0.1.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rgb2hex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rgb2hex to 0.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65p8-3hm4-h9h8 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-65p8-3hm4-h9h8 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-65p8-3hm4-h9h8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-65p8-3hm4-h9h8 in your dependencies?
O3 Security finds GHSA-65p8-3hm4-h9h8 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.