VYPR

Bitnami package

node

pkg:bitnami/node

Vulnerabilities (141)

  • CVE-2026-56850MedJul 30, 2026
    affected < 22.23.2fixed 22.23.2

    A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x*

  • CVE-2026-56847MedJul 30, 2026
    affected < 22.23.2fixed 22.23.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-48936LowJun 26, 2026
    affected >= 26.3.0, < 26.3.1fixed 26.3.1

    A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the `--allow-net` permission. This vulnerability affects one supported release line: **Node.js 26**.

  • CVE-2026-48935LowJun 26, 2026
    affected >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 >= 22.22.3, < 22.23.0fixed 22.23.0

    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 < 22.23.0fixed 22.23.0

    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 < 22.23.0fixed 22.23.0

    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 < 22.23.0fixed 22.23.0

    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-21717MedMar 30, 2026
    affected < 20.20.2fixed 20.20.2

    A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade perfo

  • CVE-2026-21716LowMar 30, 2026
    affected < 20.20.2fixed 20.20.2

    An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents (`fs.fchmod()`, `fs.fchown()`) were correctly patched. As a result, code running under `

  • CVE-2026-21715LowMar 30, 2026
    affected < 20.20.2fixed 20.20.2

    A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync.native()` without the required read permission checks, while all comparable filesystem functions correctly enforce them. As a result, code running under `--permission` with restricted `--allow-fs

  • CVE-2026-21714MedMar 30, 2026
    affected < 20.20.2fixed 20.20.2

    A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned

  • CVE-2026-21713MedMar 30, 2026
    affected < 20.20.2fixed 20.20.2

    A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possibl

  • CVE-2026-21711MedMar 30, 2026
    affected >= 25.0.0, < 25.8.2fixed 25.8.2

    A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks, while all comparable network paths correctly enforce them. As a result, code running under `--permission` without `--allow-net` can

Page 2 of 8