VYPR

rpm package

almalinux/nodejs-npm

pkg:rpm/almalinux/nodejs-npm

Vulnerabilities (58)

  • CVE-2026-56847MedJul 30, 2026
    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

  • CVE-2026-14257HigJul 23, 2026
    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

  • CVE-2026-59874HigJul 8, 2026
    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

  • CVE-2026-59873HigJul 8, 2026
    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

  • CVE-2026-13149HigJun 30, 2026
    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

  • CVE-2026-48935LowJun 26, 2026
    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**.

  • CVE-2026-48934MedJun 26, 2026
    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**.

  • CVE-2026-48933HigJun 26, 2026
    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**.

  • CVE-2026-48930CriJun 26, 2026
    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**.

  • CVE-2026-48928MedJun 26, 2026
    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**.

  • CVE-2026-48619HigJun 26, 2026
    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**.

  • CVE-2026-48618MedJun 26, 2026
    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

  • CVE-2026-48615HigJun 26, 2026
    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

  • CVE-2026-48931LowJun 22, 2026
    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**.

  • CVE-2026-48937HigJun 18, 2026
    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**.

  • CVE-2026-48617HigJun 18, 2026
    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

  • CVE-2026-9678MedJun 17, 2026
    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

  • CVE-2026-6733LowJun 17, 2026
    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

  • CVE-2026-11525LowJun 17, 2026
    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.

  • CVE-2026-12151HigJun 17, 2026
    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