rpm package
almalinux/nodejs-npm
pkg:rpm/almalinux/nodejs-npm
Vulnerabilities (58)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-56847 | Med | 6.1 | < 1:10.9.8-1.22.23.2.1.el10_2 | 1:10.9.8-1.22.23.2.1.el10_2 | Jul 30, 2026 | A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability | |
| CVE-2026-14257 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.6.el10_2 | 1:10.9.8-1.22.23.1.6.el10_2 | Jul 23, 2026 | brace-expansion through 5.0.7 is vulnerable to denial of service via memory exhaustion. The expand() function limits the number of results with a max option (default 100,000) but does not bound the length of each result string. By chaining multiple brace groups, an attacker keeps | |
| CVE-2026-59874 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.4.el10_2 | 1:10.9.8-1.22.23.1.4.el10_2 | Jul 8, 2026 | node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, tar.replace accepts a checksum-valid tar header with a negative base-256 encoded entry size, causing the archive scanner to make no progress while repeatedly parsing the same header. This issue is fixed | |
| CVE-2026-59873 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.4.el10_2 | 1:10.9.8-1.22.23.1.4.el10_2 | Jul 8, 2026 | node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.19, node-tar does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio in extraction and parsing paths such as src/extract.ts, allowing a small crafted gzip bomb to | |
| CVE-2026-13149 | Hig | — | < 1:10.9.8-1.22.23.1.4.el10_2 | 1:10.9.8-1.22.23.1.4.el10_2 | Jun 30, 2026 | brace-expansion through 5.0.6 is vulnerable to denial of service. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace groups. An attacker who passes a crafted string to expand(), directly or transitively, can cause sign | |
| CVE-2026-48935 | Low | 3.3 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with e.g. `--allow-fs-read`. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48934 | Med | 4.3 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48933 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48930 | Cri | 9.8 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48928 | Med | 5.4 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48619 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48618 | Med | 6.5 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security | |
| CVE-2026-48615 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 26, 2026 | A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers | |
| CVE-2026-48931 | Low | 3.7 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 22, 2026 | A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent the request. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**. | |
| CVE-2026-48937 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 18, 2026 | A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This vulnerability affects two supported release lines: **Node.js 22** and **Node.js 24**. | |
| CVE-2026-48617 | Hig | 8.2 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 18, 2026 | A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release | |
| CVE-2026-9678 | Med | 5.9 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 17, 2026 | Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The parser preserves the s | |
| CVE-2026-6733 | Low | 3.7 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 17, 2026 | Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request o | |
| CVE-2026-11525 | Low | 3.7 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 17, 2026 | Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. | |
| CVE-2026-12151 | Hig | 7.5 | < 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 | Jun 17, 2026 | Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and |
- affected < 1:10.9.8-1.22.23.2.1.el10_2fixed 1:10.9.8-1.22.23.2.1.el10_2
A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability
- affected < 1:10.9.8-1.22.23.1.6.el10_2fixed 1:10.9.8-1.22.23.1.6.el10_2
brace-expansion through 5.0.7 is vulnerable to denial of service via memory exhaustion. The expand() function limits the number of results with a max option (default 100,000) but does not bound the length of each result string. By chaining multiple brace groups, an attacker keeps
- affected < 1:10.9.8-1.22.23.1.4.el10_2fixed 1:10.9.8-1.22.23.1.4.el10_2
node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.18, tar.replace accepts a checksum-valid tar header with a negative base-256 encoded entry size, causing the archive scanner to make no progress while repeatedly parsing the same header. This issue is fixed
- affected < 1:10.9.8-1.22.23.1.4.el10_2fixed 1:10.9.8-1.22.23.1.4.el10_2
node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.19, node-tar does not enforce hard upper bounds on total decompressed data, entry counts, or decompression ratio in extraction and parsing paths such as src/extract.ts, allowing a small crafted gzip bomb to
- affected < 1:10.9.8-1.22.23.1.4.el10_2fixed 1:10.9.8-1.22.23.1.4.el10_2
brace-expansion through 5.0.6 is vulnerable to denial of service. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace groups. An attacker who passes a crafted string to expand(), directly or transitively, can cause sign
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with e.g. `--allow-fs-read`. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js HTTP Agent can cause a client to accept as valid a response that is send before the client has sent the request. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This vulnerability affects two supported release lines: **Node.js 22** and **Node.js 24**.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
Impact: Undici's cache interceptor incorrectly classifies some responses as cacheable when the upstream Cache-Control header uses whitespace-padded qualified private or no-cache field names such as private=" authorization" or no-cache="\tauthorization". The parser preserves the s
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
Impact: Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request o
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens.
- affected < 1:10.9.8-1.22.23.1.2.el10_2fixed 1:10.9.8-1.22.23.1.2.el10_2
Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and
Page 2 of 3