Homepage

Access of Resource Using Incompatible Type ('Type Confusion') The advisory has been revoked - it doesn't affect any version of package nodejs-devel  (opens in a new tab)

Threat Intelligence

EPSS
0.02% (6th 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 Learn

Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL10-NODEJSDEVEL-15888440
  • published4 Apr 2026
  • disclosed30 Mar 2026
Report a new vulnerability Found a mistake?

Introduced: 30 Mar 2026

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

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs-devel package and not the nodejs-devel package as distributed by RHEL.

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["__proto__"] 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