# CVE-2026-62985: request-filtering-agent: Synchronous throw from createConnection() for literal private-IP hosts bypasses req.on('error'), crashing the Node.js process

> An attacker can crash the Node.js application by triggering a synchronous exception in the request-filtering-agent when blocking private IP addresses.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** GHSA-r3r9-wp5j-pq5g

## What is CVE-2026-62985?

CVE-2026-62985 is a high-severity denial of service vulnerability in azu request-filtering-agent, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2026-62985?

2 open source packages ship an affected version, including request-filtering-agent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `request-filtering-agent` | npm | All versions | 3.2.1 |
| `request-filtering-agent` | npm | All versions | 3.2.1 |

## How do I fix CVE-2026-62985?

Upgrade request-filtering-agent to 3.2.1 or later.

## Is CVE-2026-62985 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62985 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62985 and fix it if it is affected.

What it is: CVE-2026-62985 is a high-severity denial of service vulnerability in azu request-filtering-agent, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62985 exists.

Affected packages and fixed versions:
- request-filtering-agent (npm): affected all versions; fixed in 3.2.1
- request-filtering-agent (npm): affected all versions; fixed in 3.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62985/ (Markdown: https://insights.sbomify.com/CVE-2026-62985/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62985
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62985
- OSV: https://osv.dev/vulnerability/CVE-2026-62985

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62985/
Summaries are generated and may contain mistakes; the official description above is the record.