Access of Resource Using Incompatible Type ('Type Confusion') Affecting nodejs:20/npm package, versions <1:10.8.2-1.20.20.2.2.module+el9.6.0+24220+c44c288d


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.03% (9th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-NODEJS-16135992
  • published23 Apr 2026
  • disclosed30 Mar 2026

Introduced: 30 Mar 2026

CVE-2026-21710  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

Upgrade RHEL:9 nodejs:20/npm to version 1:10.8.2-1.20.20.2.2.module+el9.6.0+24220+c44c288d or higher.
This issue was patched in RHSA-2026:9874.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:20/npm package and not the nodejs:20/npm package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

A flaw in Node.js HTTP request handling causes an uncaught TypeError when a request is received with a header named __proto__ and the application accesses req.headersDistinct.

When this occurs, dest[&#34;__proto__&#34;] resolves to Object.prototype rather than undefined, causing .push() to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by error event listeners, meaning it cannot be handled without wrapping every req.headersDistinct access in a try/catch.

  • This vulnerability affects all Node.js HTTP servers on 20.x, 22.x, 24.x, and v25.x

CVSS Base Scores

version 3.1