PatchTheCVECVE-2018-3739: https-proxy-agent before 2.1.1 passes auth option to the Buffer constructor without proper sanitization, resul
CVE-2018-3739 is a critical-severity flaw (CVSS 9.1) affecting https-proxy-agent. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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).
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-3739?
https-proxy-agent: upgrade to 2.2.0. Exact commands for each OS are on this page.
Is CVE-2018-3739 being exploited?
CVE-2018-3739 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-3739 affect?
CVE-2018-3739 affects https-proxy-agent. Severity is critical (CVSS 9.1). 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)
How urgent is CVE-2018-3739?
Priority 61/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action