Denial of Service in https-proxy-agent
Summary
GHSA-qrg3-f6h6-vq8q: Denial of Service in https-proxy-agent. Affects https-proxy-agent versions < 2.2.0. Fixed in 2.2.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package under scrutiny is https-proxy-agent, an npm package used for creating an HTTP or HTTPS proxy agent. It allows applications to make HTTP or HTTPS requests via a proxy server. This vulnerability affects versions prior to 2.2.0.
Vulnerability Detail
The vulnerability, identified as GHSA-qrg3-f6h6-vq8q, is a Denial of Service (DoS) issue. It has been marked as a duplicate of GHSA-8g7p-74h8-hg48. The specific technical details of the vulnerability are not provided in the available information.
How To Fix
Latest published version: 9.1.0 as of 22 Oct 2026
npm install https-proxy-agent@9.1.0
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.2.0
This is the first release that contains the fix.
npm install https-proxy-agent@2.2.0
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The vulnerability GHSA-qrg3-f6h6-vq8q in the https-proxy-agent package is a Denial of Service issue. It is recommended to update to version 2.2.0 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for https-proxy-agent →
FAQ
The impact of this vulnerability is not specified in the available information.
No workaround is mentioned for this vulnerability.
You can use Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. No signup is required, and you can simply input your package-lock.json file to get real-time alerts for open-source vulnerabilities.
For more information about this vulnerability, you can reach out to info@devnack.com.
If you have discovered a new vulnerability, you can report it to the package maintainer or the relevant security team.
References
Related vulnerabilities
Recent vulnerabilities recorded for https-proxy-agent.