SB2026083146 - Red Hat Enterprise Linux 10 update for nodejs22
Published: August 31, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 3 vulnerabilities.
1) Allocation of Resources Without Limits or Throttling (CVE-ID: CVE-2026-14257)
CWE-ID: CWE-770 - Allocation of Resources Without Limits or Throttling
CVSSv4: 8.7 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to cause a denial of service.
The vulnerability exists due to uncontrolled resource consumption in expand() when processing attacker-influenced brace expansion patterns. A remote attacker can send a specially crafted input string to cause a denial of service.
The issue can terminate the Node process with an uncatchable out-of-memory error.
2) Resource exhaustion (CVE-ID: CVE-2026-69152)
CWE-ID: CWE-400 - Resource exhaustion
CVSSv4: 8.7 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to cause a denial of service.
The vulnerability exists due to uncontrolled resource consumption in the expand() function when processing attacker-controlled brace patterns. A remote attacker can send a specially crafted input to cause a denial of service.
The issue can terminate the Node process with an uncatchable out-of-memory error or block the event loop for an extended period.
3) Server-Side Request Forgery (SSRF) (CVE-ID: CVE-2026-69192)
CWE-ID: CWE-918 - Server-Side Request Forgery (SSRF)
CVSSv4: 6.9 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to bypass network trust boundaries and perform server-side request forgery.
The vulnerability exists due to improper input validation in the Address4 parser when processing user-supplied IPv4 addresses with leading-zero octets. A remote attacker can supply a specially crafted address string to bypass network trust boundaries and perform server-side request forgery.
This issue occurs because the library interprets leading-zero octets as decimal while common URL parsers and resolvers interpret them as octal, causing security checks such as private-address and subnet classification to disagree with the destination actually reached by the network stack.
Remediation
Install update from vendor's website.