NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Uncontrolled resource consumption in jpeg-jsGHSA-w7q9-p3jq-fmhm

MEDIUMFix: eugeneware/jpeg-js@135705b

GHSA-w7q9-p3jq-fmhm is a medium-severity (CVSS 5.5) Uncontrolled Resource Consumption 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.

Also known asCVE-2020-8175
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk
0.00%0.53%1.05%1.58%0.2%1.1%May 26Sep 26Nov 26

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

1 pkg affected

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.

754other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
jpeg-jsnpm
21.9Mdownloads / week

Description

Uncontrolled resource consumption in jpeg-js before 0.4.0 may allow attacker to launch denial of service attacks using specially a crafted JPEG image.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjpeg-jsall versions0.4.0npm install jpeg-js@0.4.0

Affected Products

1 product · 1 configurations
Application
jpeg-jsjpeg-js_project
< 0.4.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Uncontrolled resource consumption in `jpeg-js` before 0.4.0 may allow at…

hackerone.comNVDJul 2020

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update jpeg-js to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w7q9-p3jq-fmhm is resolved across your whole dependency graph.

  3. 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

Uncontrolled resource consumption in `jpeg-js` before 0.4.0 may allow attacker to launch denial of service attacks using specially a crafted JPEG image.
O3 Security · Impact-Aware SCA

Is GHSA-w7q9-p3jq-fmhm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Uncontrolled resource consumption in jpeg-js (Medium 5.5)