Access of Resource Using Incompatible Type ('Type Confusion') Affecting npm package, versions <1:11.11.0-1.24.14.1.2.module+el8.10.0+24190+49a46c75


Severity

Recommended
0.0
high
0
10

Based on CentOS security rating.

Threat Intelligence

Social Trends
EPSS
26.36% (98th 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-CENTOS8-NPM-15893490
  • published4 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 Centos:8 npm to version 1:11.11.0-1.24.14.1.2.module+el8.10.0+24190+49a46c75 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream npm package and not the npm package as distributed by Centos. See How to fix? for Centos:8 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