CVE-2026-62985 azu CVE debrief

Who should care

Defenders responsible for Node.js applications using the request-filtering-agent should assess exposure and prioritize upgrading to version 3.2.1 or later to prevent potential application process termination due to uncaught exceptions.

Why it matters

CVE-2026-62985 is a high-severity vulnerability in the request-filtering-agent that can lead to application process termination. Defenders should prioritize upgrading to version 3.2.1 or later and review error handling configurations.

• Potential application process termination due to uncaught exceptions
• Asynchronous error delivery asymmetry in Node.js http.request and http.get
• Need for verification of affected versions and exploitation

Technical summary

The request-filtering-agent, an HTTP(S) agent that blocks requests to private/reserved IP addresses, had a vulnerability prior to version 3.2.1. Synchronous throws from createConnection occurred when rejecting literal private-IP hosts, such as 169.254.169.254 or 127.0.0.1, bypassing req.on('error') and potentially terminating the application process. Hostnames resolved through the asynchronous lookup path were not affected. This issue is fixed in version 3.2.1.

Defensive priority

Defenders should prioritize upgrading to version 3.2.1 or later to prevent potential application process termination due to uncaught exceptions.

Recommended defensive actions

• Upgrade to version 3.2.1 or later
• Review application process error handling
• Verify IP address filtering configurations
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source references indicate that the issue is fixed in version 3.2.1. However, details on affected versions and exploitation are limited. Defenders should verify IP address filtering configurations and review error handling mechanisms to ensure they are properly configured to handle potential exceptions. Additionally, defenders should assess the exposure of Node.js applications using the request-filtering-agent and prioritize upgrading to version 3.2.1 or later. Limited source detail is available, so explicit evidnce

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.