CVE-2026-2229 Affecting nodejs-full-i18n package, versions <1:24.14.1-2.module+el8.10.0+90873+35652ecc


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.2% (43rd 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-ORACLE8-NODEJSFULLI18N-16002031
  • published13 Apr 2026
  • disclosed12 Mar 2026

Introduced: 12 Mar 2026

CVE-2026-2229  (opens in a new tab)

How to fix?

Upgrade Oracle:8 nodejs-full-i18n to version 1:24.14.1-2.module+el8.10.0+90873+35652ecc or higher.
This issue was patched in ELSA-2026-7670.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs-full-i18n package and not the nodejs-full-i18n package as distributed by Oracle. See How to fix? for Oracle:8 relevant fixed versions and status.

ImpactThe undici WebSocket client is vulnerable to a denial-of-service attack due to improper validation of the server_max_window_bits parameter in the permessage-deflate extension. When a WebSocket client connects to a server, it automatically advertises support for permessage-deflate compression. A malicious server can respond with an out-of-range server_max_window_bits value (outside zlib's valid range of 8-15). When the server subsequently sends a compressed frame, the client attempts to create a zlib InflateRaw instance with the invalid windowBits value, causing a synchronous RangeError exception that is not caught, resulting in immediate process termination.

The vulnerability exists because:

  • The isValidClientWindowBits() function only validates that the value contains ASCII digits, not that it falls within the valid range 8-15
  • The createInflateRaw() call is not wrapped in a try-catch block
  • The resulting exception propagates up through the call stack and crashes the Node.js process

CVSS Base Scores

version 3.1