p PatchFirst

PatchFirst · Latest vulnerabilities

Node.js stack vulnerabilities · Page 97

Vulnerabilities published for Node.js in the last 30 days: 385. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Node.js

Early warnings

Fresh vulnerability reports from vendor announcements and security news. These warnings do not change the security rating.

  1. node.js

    No fix published

    Node.js: denial of service

    According to GitHub Advisory Database, Node.js has a denial of service vulnerability (CVE-2026-109932). The exact affected versions are unspecified. The report does not name a fixed version.

    What to do now: Check whether a Node.js update with the fix is available and install it.

    CVE-2026-109932

  2. node.js

    No fix published

    Node.js: remote code execution

    According to OpenNet, Node.js has a remote code execution vulnerability (CVE-2026-111497). The exact affected versions are unspecified. The report does not name a fixed version.

    What to do now: Check whether a Node.js update with the fix is available and install it.

    CVE-2026-111497

Vulnerabilities: 7795

  1. CVE-2026-22706

    Low · CVSS 2.1EPSS 0.34%Fix available

    Strapi: Password Reset Does Not Revoke Existing Refresh Sessions

    Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, changing or resetting a user's password did not invalidate the user's existing refresh-token sessions by default. The refresh-token invalidation step in the users-permissions and admin authentication controllers was conditional on a caller-supplied `deviceId`. When a password change or reset request did not include a `deviceId`, no refresh tokens were revoked, leaving every prior session active. An attacker who had previously obtained a refresh token could continue minting new access tokens after the legitimate user reset their password, allowing

    • Update to 5.33.3
    Published Updated
  2. CVE-2026-22599

    Critical · CVSS 9.3EPSS 1.18%Public exploitFix available

    Strapi Vulnerable to SQL Injection in Content Type Builder

    Strapi is an open source headless content management system. In versions on the 4.x branch prior to 4.26.1 and on the 5.x branch prior to 5.33.2, a database-query injection vulnerability existed in the Strapi Content-Type Builder write API. An authenticated administrator could inject arbitrary database statements through the `column.defaultTo` attribute when creating or modifying a content type. Setting `defaultTo` as a tuple `[value, { isRaw: true }]` caused the value to be passed directly into Knex's `db.connection.raw()` during schema migration without sanitization, allowing arbitrary statement execution at the database layer. Depending on

    • Update to 4.26.1
    • Update to 5.33.2
    Published Updated
  3. CVE-2026-44589

    Low · CVSS 3.7EPSS 0.17%Fix available

    nuxt-og-image SSRF — bypass of GHSA-pqhr-mp3f-hrpp / v6.2.5 fix (IPv6 + redirect)

    Nuxt OG Image generates OG Images with Vue templates in Nuxt. The isBlockedUrl() denylist introduced in [email protected] to remediate GHSA-pqhr-mp3f-hrpp (Dmitry Prokhorov / Positive Technologies, March 2026) is incomplete. It has an incomplete IPv6 prefix list and is missing redirect re-validation. This vulnerability is fixed in 6.4.9.

    • Update to 6.4.9
    Published Updated
  4. CVE-2025-64526

    Medium · CVSS 6.9EPSS 0.49%Fix available

    Strapi has a rate limit bypass on users-permissions plugin via attacker-controlled email keying

    Strapi is an open source headless content management system. In Strapi versions prior to 5.45.0, the rate-limit middleware in the users-permissions plugin derived its rate-limit key in part from `ctx.request.body.email`, including on routes whose body schema does not contain an `email` field (`/auth/local`, `/auth/reset-password`, `/auth/change-password`). An unauthenticated attacker could include an arbitrary `email` value in the request body to obtain a fresh rate-limit key per request, effectively bypassing per-IP throttling on those routes and enabling high-volume credential brute-force, password-reset code brute-force, and credential-stu

    • Update to 5.45.0
    Published Updated
  5. GHSA-7rx4-c5vx-g8w3

    High · CVSS 7.1Fix available

    Karakeep SDK has SSRF via metascraper-logo-favicon that bypasses validateUrl protections

    ## Summary The `metascraper-logo-favicon` plugin makes HTTP requests to URLs extracted from attacker-controlled HTML without going through the application's `validateUrl()` SSRF protections. This allows any authenticated user to make the server fetch arbitrary internal URLs by bookmarking a page containing a crafted `<link rel="icon">` tag. ## Details ### Protected path (correct) Karakeep implements comprehensive SSRF protections in `apps/workers/network.ts` (lines 12-222). The `validateUrl()` function blocks loopback, private, link-local, carrier-grade NAT, and reserved IP ranges. It resolves DNS before the fetch and checks all resolved

    • Update to 0.32.0
    Published Updated
  6. CVE-2026-42334

    High · CVSS 7.5EPSS 0.27%Fix available

    Mongoose: Improper Sanitization of $nor in sanitizeFilter May Allow NoSQL Injection

    Mongoose is a MongoDB object modeling tool designed to work in an asynchronous environment. Prior to 6.13.9, 7.8.9, 8.22.1, and 9.1.6, a vulnerability allows bypassing Mongoose’s sanitizeFilter query sanitization mechanism via the $nor operator. When sanitizeFilter is enabled, Mongoose wraps query operators in $eq to neutralize them. However, prior to the fix, $nor was not included in the set of logical operators that are recursively sanitized. Because $nor accepts an array (like $and and $or), and arrays do not trigger hasDollarKeys(), malicious operators such as $ne, $gt, or $regex could be injected inside a $nor clause without being saniti

    • Update to 6.13.9
    • Update to 7.8.9
    • Update to 8.22.1
    • Update to 9.1.6
    Published Updated
  7. GHSA-9m65-766c-r333

    Medium · CVSS 6.3Fix available

    TanStack Start - Server Core: Inbound server-function request deserialization could invoke a sibling client-referenced server function

    ### Summary A type-confusion bug in seroval ≤ 1.5.2 ([upstream advisory](https://github.com/lxsmnsyc/seroval/security/advisories)) allowed a crafted JSON body sent to one TanStack Start server function to trigger invocation of a different client-referenced server function as a side effect of deserializing the request payload. This is not an authentication bypass and not remote code execution. The mechanism only invokes server functions that the same client could already reach directly via /_serverFn/<id>, and the target function's full middleware chain — including any user-supplied authentication, authorization, and inputValidator — runs as

    • Update to 1.167.30
    Published Updated
  8. CVE-2026-44503

    High · CVSS 7EPSS 0.64%Fix available

    Kiota abstractions RedirectHandler leaks Cookie/Proxy-Authorization headers on cross-host redirect

    The RedirectHandler middleware in microsoft/kiota-java (com.microsoft.kiota:microsoft-kiota-http-okHttp v1.9.0) and other Kiota libraries fails to strip sensitive HTTP headers when following 3xx redirects to a different host or scheme. Only the Authorization header is removed; Cookie, Proxy-Authorization, and all custom headers are forwarded to the redirect target.

    • Update to 1.0.0-preview.100
    • Update to 1.22.0
    • Update to 1.5.5
    • Update to 1.9.1
    • Update to 1.9.9
    Published Updated
  9. CVE-2026-42281

    Critical · CVSS 9.2EPSS 1.62%Public exploitFix available

    MagicMirror²: Unauthenticated SSRF via /cors endpoint

    MagicMirror² is an open source modular smart mirror platform. Prior to 2.36.0, an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the /cors endpoint allows any remote attacker to force the MagicMirror² server to perform arbitrary HTTP requests to internal networks, cloud metadata services, and localhost services. The endpoint also expands environment variable placeholders (**VAR_NAME**), enabling exfiltration of server-side secrets. This vulnerability is fixed in 2.36.0.

    • Update to 2.36.0
    Published Updated
  10. CVE-2026-44374

    Medium · CVSS 4.3EPSS 0.17%Fix available

    Backstage: Catalog unprocessed read endpoints allow authenticated cross-owner data access without permission checks

    Backstage is an open framework for building developer portals. Prior to 0.6.11, the unprocessed entities read endpoints in @backstage/plugin-catalog-backend-module-unprocessed do not enforce permission authorization checks. Any authenticated user can access unprocessed entity records regardless of ownership. This is an information disclosure vulnerability affecting Backstage installations using this module. This is patched in @backstage/plugin-catalog-backend-module-unprocessed version 0.6.11, @backstage/plugin-catalog-unprocessed-entities-common version 0.0.15 and @backstage/plugin-catalog-unprocessed-entities version 0.2.30.

    • Update to 0.0.15
    • Update to 0.2.30
    • Update to 0.6.11
    Published Updated
  11. CVE-2026-42559

    High · CVSS 8.8EPSS 0.27%Fix available

    RMCP: DNS rebinding vulnerability in rmcp Streamable HTTP server transport

    RMCP is an official Rust SDK for the Model Context Protocol. Prior to version 1.4.0, the rmcp crate's Streamable HTTP server transport (crates/rmcp/src/transport/streamable_http_server/) did not validate the incoming Host header. This allowed a malicious public website, via a DNS rebinding attack, to send authenticated requests to an MCP server running on the victim's loopback or private-network interface. This vulnerability is fixed in 1.4.0.

    • Update to 0.9.13
    Published Updated
  12. CVE-2026-44437

    Medium · CVSS 6.9EPSS 0.2%Fix available

    Angular SSR: Open Redirect and Request Steering via Encoded X-Forwarded-Prefix

    The Angular SSR is a server-rise rendering tool for Angular applications. From 19.0.0-next.0 to before 19.2.25, 20.3.25, 21.2.9, and 22.0.0-next.7, a vulnerability exists in the X-Forwarded-Prefix header processing logic within Angular SSR. The internal validation mechanism fails to properly account for URL-encoded characters, specifically dots (%2e%2e). This allows an attacker to bypass security filters by injecting encoded path traversal sequences that are later decoded and utilized by the application logic. When an Angular SSR application is configured to trust proxy headers and is deployed behind a proxy that forwards the X-Forwarded-Pref

    • Update to 19.2.25
    • Update to 20.3.25
    • Update to 21.2.9
    • Update to 22.0.0-next.7
    Published Updated
  13. CVE-2026-44372

    Medium · CVSS 5.3EPSS 0.28%Fix available

    Nitro: Open Redirect via Protocol-Relative URL Bypass in Wildcard Route Rules

    Nitro is a next generation server toolkit. Prior to 3.0.260429-beta, an attacker could turn a redirect route rule using wildcards rewrite into a cross-host redirect by sliding an extra slash in after the rule prefix. This vulnerability is fixed in 3.0.260429-beta.

    • Update to 2.13.4
    • Update to 3.0.260429-beta
    Published Updated
  14. CVE-2026-44373

    Medium · CVSS 5.3EPSS 0.45%Fix available

    Nitro: Proxy scope bypass via percent-encoded path traversal in `routeRules`

    Nitro is a next generation server toolkit. Prior to 3.0.260429-beta, an attacker could bypass a proxy route rule by sending percent-encoded path traversal (..%2f) in the URL, causing Nitro to forward a request that the upstream resolved outside the configured scope. This vulnerability is fixed in 3.0.260429-beta.

    • Update to 2.13.4
    • Update to 3.0.260429-beta
    Published Updated
  15. CVE-2026-44351

    Critical · CVSS 9.1EPSS 0.25%Fix available

    fast-jwt: Empty HMAC secret accepted via async key resolver - JWT auth bypass

    fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.2.4, a critical authentication-bypass vulnerability in fast-jwt's async key-resolver flow allows any unauthenticated attacker to forge arbitrary JWTs that are accepted as authentic. When the application's key resolver returns an empty string (''), for example via the common keys[decoded.header.kid] || '' JWKS-style fallback, fast-jwt converts it to a zero-length Buffer, hands it to crypto.createSecretKey, derives allowedAlgorithms = ['HS256','HS384','HS512'] from it, and then verifies the token's signature against an empty-key HMAC. The attacker simply computes HMAC-SHA256

    • Update to 6.2.4
    Published Updated
  16. CVE-2026-44005

    Critical · CVSS 10EPSS 0.83%Fix available

    vm2: Sandbox escape

    vm2 is an open source vm/sandbox for Node.js. From 3.9.6 to 3.10.5, vm2's bridge exposes mutable proxies for real host-realm intrinsic prototypes and then forwards sandbox writes into the underlying host objects with otherReflectSet() and otherReflectDefineProperty(), which lets attacker-controlled JavaScript running in a default VM or inherited NodeVM mutate shared host Object.prototype, Array.prototype, and Function.prototype from inside the sandbox This vulnerability is fixed in 3.11.0.

    • Update to 3.11.0
    Published Updated
  17. CVE-2026-45411

    Critical · CVSS 9.8EPSS 0.57%Fix available

    vm2: Sandbox Breakout Using Async Generator

    vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.3, it is possible to catch a host exception using the yield* expression inside an async generator. When the generator is closed using the return function, the value is awaited on and exceptions thrown in the then call will be caught by the runtime and passed to the yield* iterator as the next value. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.3.

    • Update to 3.11.3
    Published Updated
  18. CVE-2026-44008

    Critical · CVSS 9.8EPSS 0.85%Fix available

    vm2: Snabox breakout via `neutralizeArraySpeciesBatch`

    vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.2, the new method neutralizeArraySpeciesBatch works with objects from the other side but can call into this side via getter on the array prototype exposing objects of the wrong side into the sandbox. This can be used to get host objects and get the host Function object. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.2.

    • Update to 3.11.2
    Published Updated
  19. CVE-2026-44007

    Critical · CVSS 9.1EPSS 0.96%Fix available

    vm2: nesting: true bypasses require: false, allowing sandbox escape to arbitrary OS command execution

    vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.1, when a NodeVM is created with nesting: true, sandbox code can unconditionally require('vm2') regardless of the outer VM's require configuration — including require: false. With access to vm2, the sandbox constructs a new inner NodeVM with its own unrestricted require settings and executes arbitrary OS commands on the host. Any application that runs untrusted code inside a NodeVM with nesting: true is fully compromised. This vulnerability is fixed in 3.11.1.

    • Update to 3.11.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →