Request Filtering Agent Security Update Addresses 1 Vulnerability
Tech GuruQuick Answer
request-filtering-agent before 3.2.1 can crash a Node.js application while rejecting a literal private-IP destination. The rejection throws synchronously, bypassing the request's normal error listener. Update the deployed dependency to 3.2.1; this issue concerns error handling, not proof that the blocked request reaches the private service.
Confirm Scope And Apply The Supported Fix
What to do now: Identify applications that pass user-controlled destinations to the filtering HTTP/HTTPS agents. Update their lockfiles and deployed packages, then test rejected destinations in an isolated process.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Request Filtering Agent packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-r3r9-wp5j-pq5g |
| CVE | CVE-2026-62985 |
| Project advisory publication | 2026-06-29 02:29:21 UTC |
| Recorded source timestamp (historical snapshot) | 2026-09-22 19:54:19 UTC |
| Affected versions | request-filtering-agent < 3.2.1 |
| Fixed version | request-filtering-agent 3.2.1 |
| CVSS base score | 7.5 (CVSS v3) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
For literal private-IP hosts, createConnection() throws before an asynchronous request error can reach req.on('error'). The DNS-lookup path for hostnames already reports errors asynchronously and is not affected by this asymmetry. An attacker must be able to make the application attempt such a request; mere dependency presence does not establish that input path.
What To Validate Now
- Inventory. Locate Request Filtering Agent packages and release streams identified in the project advisories deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: request-filtering-agent < 3.2.1 Do not infer applicability from product family or severity alone.
- Remediate. Apply request-filtering-agent 3.2.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. With controlled fixtures, check that forbidden literal-IP and DNS-resolved destinations are rejected through the expected error path without terminating the process, while permitted requests still work. Keep private-destination filtering enabled.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
The GHSA's old package panel still lists no patch, but the current GitHub CNA explicitly identifies 3.2.1 as fixed and links its release. Do not work around the crash by disabling destination checks or merely swallowing all uncaught process exceptions.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
