GHSA-xvf7-4v9q-58w6 is a high-severity (CVSS 7.5) CWE-835 vulnerability in jpeg-js. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for jpeg-js — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
jpeg-jsnpmDescription
The package jpeg-js before 0.4.4 is vulnerable to Denial of Service (DoS) where a particular piece of input will cause the program to enter an infinite loop and never return.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | jpeg-js | all versions | 0.4.4npm install jpeg-js@0.4.4 |
Affected Products
jpeg-jsjpeg-js_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jpeg-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jpeg-js to 0.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvf7-4v9q-58w6 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-xvf7-4v9q-58w6 in your dependencies?
Find it across npm, including transitive dependencies.