Versions of http-proxy-agent before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to Buffer.
Full advisory text at GitHub advisory.
http-proxy-agent (npm) has 2 known vulnerabilities, the worst rated HIGH. Upgrade to 2.1.0 or later to clear all of them. No malicious-package signal is recorded.
39 packages depend on it
an advisory here reaches each of them
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
severity band, no base score published
chance of exploitation in 30 days
CyberXYZ composite out of 10
fig. 01 — GHSA-8w57-jfpm-945m, the advisory selected below
Versions of http-proxy-agent before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to Buffer.
Full advisory text at GitHub advisory.
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for http-proxy-agent (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 2 known vulnerabilities for http-proxy-agent (npm), the worst rated HIGH. They are GHSA-8w57-jfpm-945m, GHSA-86wf-436m-h424.
2.1.0 or later clears every advisory recorded for http-proxy-agent (npm). Check the release you pick before installing it.
Search http-proxy-agent in CyberXYZ Check at https://cyberxyz.io/check?q=http-proxy-agent. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:58 UTC. The most recent advisory here was published 2022-01-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.