The IsAllowedHost check in https://github.com/nodejs/node/blob/fdf0a84e826d3a9ec0ce6f5a3f5adc967fe99408/src/inspector_socket.cc#L580 can easily be bypassed because IsIPAddress does not properly…

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2022-32212: 6.43% estimated exploitation activity in the next 30 days; percentile 93.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The IsAllowedHost check in https://github.com/nodejs/node/blob/fdf0a84e826d3a9ec0ce6f5a3f5adc967fe99408/src/inspector_socket.cc#L580 can easily be bypassed because IsIPAddress does not properly check if an IP address is invalid or not. When an invalid IPv4 address is provided (for instance 10.0.2.555 is provided), the browser will make a DNS requests to the DNS server, providing a vector for an attacker-controlled DNS server to perform a rebinding attack and hence access the JSON file containing the WebSocket file. The fix we introduced in https://hackerone.com/reports/1069487 was not complete.

Published by the source

23 Sep 2022, 00:00 UTC

Last modified by the source

23 Sep 2022, 00:00 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 2 · published · 26 Oct 2026

   Published from vendor_advisory record nodejs-security-wg:core:96

2. Revision 1 · created · 26 Oct 2026

   Created from vendor_advisory record nodejs-security-wg:core:96

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-32212

Advisory: The IsAllowedHost check in https://github.com/nodejs/node/blob/fdf0a84e826d3a9ec0ce6f5a3f5adc967fe99408/src/inspector_socket.cc#L580 can easily be bypassed because IsIPAddress does not properly…
IDs: CVE-2022-32212
Record: https://patchnext.com/advisories/cve-2022-32212 (revision 2, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node 18.9.1, 16.17.1, 14.20.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- runtime node: affected >= 14.0.0, < 14.20.1; >= 16.0.0, < 16.17.1; >= 18.0.0, < 18.9.1; fixed in 18.9.1, 14.20.1, 16.17.1

## Suggested inspection (read-only)
- runtime node: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://nodejs.org/dist/index.json (The nodejs.org release index dates the first patched release for CVE-2022-32212 to 2022-09-23.)
- Verified: https://raw.githubusercontent.com/nodejs/security-wg/main/vuln/core/96.json (Node.js security working group core entry 96 lists CVE-2022-32212 affecting node >=14.0.0 =16.0.0 =18.0.0 <18.9.1)

Commands are suggestions: review each one before running it.