EUVD-2026-84679
GHSA-r3r9-wp5j-pq5g
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attacker-supplied literal private IP reaches the agent over the network with no auth or interaction, causing a process-crash DoS; no confidentiality or integrity impact, so C:N/I:N/A:H.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
5Blast Radius
ecosystem impact- 22 npm packages depend on request-filtering-agent (11 direct, 11 indirect)
Ecosystem-wide dependent count for version 3.2.1.
DescriptionCVE.org
request-filtering-agent is an http(s).Agent implementation that blocks requests to Private/Reserved IP addresses. Prior to 3.2.1, RequestFilteringHttpAgent and RequestFilteringHttpsAgent synchronously threw from createConnection when rejecting a literal private-IP host such as 169.254.169.254 or 127.0.0.1. Because Node.js http.request and http.get expect connection failures to be delivered asynchronously, the throw bypassed req.on('error') and became an uncaught exception that could terminate the application process. Hostnames resolved through the asynchronous lookup path were not affected by this error-delivery asymmetry. This issue is fixed in version 3.2.1.
Articles & Coverage 1
AnalysisAI
Denial of service in the request-filtering-agent npm package (all versions prior to 3.2.1) lets remote attackers terminate a Node.js process by causing the application to request a literal private or reserved IP address such as 127.0.0.1 or the cloud-metadata address 169.254.169.254. RequestFilteringHttpAgent and RequestFilteringHttpsAgent threw synchronously from createConnection when rejecting such a literal IP; because Node's http.request/http.get expect connection failures to arrive asynchronously, the throw escaped req.on('error') and surfaced as an uncaught exception that crashes the process (CWE-248). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires a consuming application that (1) makes outbound requests through RequestFilteringHttpAgent or RequestFilteringHttpsAgent and (2) allows an attacker to influence the request host with a LITERAL private/reserved IP address (e.g., 127.0.0.1 or the cloud-metadata address 169.254.169.254). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are internally consistent and point to a genuine but bounded availability risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade request-filtering-agent to version 3.2.1 or later, which replaces the synchronous `throw validationError` in both RequestFilteringHttpAgent and RequestFilteringHttpsAgent with a createConnectionErrorSocket() return so the rejection is delivered through the connectionListener (or via socket.destroy(error)), preserving Node's asynchronous error contract; see the advisory https://github.com/azu/request-filtering-agent/security/advisories/GHSA-r3r9-wp5j-pq5g, the fix commit https://github.com/azu/request-filtering-agent/commit/9d12561064524807fc399158eaa5bd7a40dd8cd0, and the release at https://github.com/azu/request-filtering-agent/releases/tag/v3.2.1. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every service and dependency tree that pulls in request-filtering-agent (for example, npm ls request-filtering-agent) and confirm exposure where versions are below 3.2.1; because the status is 'No vendor-released patch identified at time of analysis,' do not wait for a fix - instead reduce blast radius immediately by running affected Node.js processes under a supervisor configured for automatic restart (systemd Restart=always, PM2, or a Kubernetes restartPolicy), and add alerting on unexpected process restarts as an early-warning signal for exploitation attempts. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-248 – Uncaught Exception
View allShare
External POC / Exploit Code
Leaving vuln.today