Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Denial of Service in https-proxy-agentGHSA-8g7p-74h8-hg48

CRITICALFix: TooTallNate/node-https-proxy-agent@1c24219

GHSA-8g7p-74h8-hg48 is a critical-severity (CVSS 9.1) Uncontrolled Resource Consumption vulnerability in https-proxy-agent. 1 public exploit reference exists, so weaponization risk is real. A fix is available for https-proxy-agent — see the affected versions and patch details below.

Also known asCVE-2018-3739
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk-0.28%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.00%0.84%1.67%2.51%0.4%1.7%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-8g7p-74h8-hg48 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

6Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
https-proxy-agentnpm
174.7Mdownloads / week

Description

https-proxy-agent before 2.1.1 passes auth option to the Buffer constructor without proper sanitization, resulting in DoS and uninitialized memory leak in setups where an attacker could submit typed input to the 'auth' parameter (e.g. JSON).

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmhttps-proxy-agentall versions2.2.0npm install https-proxy-agent@2.2.0

Affected Products

1 product · 1 configurations
Application
https-proxy-agenthttps-proxy-agent_project
< 2.2.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.

https-proxy-agent before 2.1.1 passes auth option to the Buffer construc…

hackerone.comNVDOct 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update https-proxy-agent to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8g7p-74h8-hg48 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

Versions of `https-proxy-agent` before 2.2.0 are vulnerable to denial of service. This is due to unsanitized options (proxy.auth) being passed to `Buffer()`. ## Recommendation Update to version 2.2.0 or later.
O3 Security · Impact-Aware SCA

Is GHSA-8g7p-74h8-hg48 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Denial of Service in https-proxy-agent (Critical 9.1)