p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de la pile Node.js · Page n° 160

Vulnérabilités publiées pour Node.js au cours des 30 derniers jours : 390. Présentes dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Node.js

Alertes précoces

Signalements récents de vulnérabilités issus des annonces des éditeurs et de l’actualité de la sécurité. Ces alertes ne modifient pas la note de sécurité.

  1. node.js

    Aucun correctif publié

    Node.js : exécution de code à distance

    Selon OpenNet, Node.js présente une vulnérabilité d’exécution de code à distance (CVE-2026-111497). Les versions exactes affectées ne sont pas précisées. Le message ne précise pas de version corrigée.

    Que faire maintenant : Vérifiez si une mise à jour de sécurité de Node.js contenant le correctif est disponible et installez-la.

    CVE-2026-111497

  2. node.js

    Aucun correctif publié

    Node.js : déni de service

    Selon GitHub Advisory Database, Node.js présente une vulnérabilité de déni de service (CVE-2026-109932). Les versions exactes affectées ne sont pas précisées. Le message ne précise pas de version corrigée.

    Que faire maintenant : Vérifiez si une mise à jour de sécurité de Node.js contenant le correctif est disponible et installez-la.

    CVE-2026-109932

Vulnérabilités : 7800

  1. CVE-2026-27729

    Moyenne · CVSS 5.9EPSS 0,48%Correctif disponible

    Astro has memory exhaustion DoS due to missing request body size limit in Server Actions

    Astro is a web framework. In versions 9.0.0 through 9.5.3, Astro server actions have no default request body size limit, which can lead to memory exhaustion DoS. A single large POST to a valid action endpoint can crash the server process on memory-constrained deployments. On-demand rendered sites built with Astro can define server actions, which automatically parse incoming request bodies (JSON or FormData). The body is buffered entirely into memory with no size limit — a single oversized request is sufficient to exhaust the process heap and crash the server. Astro's Node adapter (`mode: 'standalone'`) creates an HTTP server with no body size

    • Mettez à jour vers 9.5.4
    Publication Mise à jour
  2. CVE-2026-25545

    Moyenne · CVSS 6.9EPSS 1,93%Code d’exploitation publicCorrectif disponible

    Astro has Full-Read SSRF in error rendering via Host: header injection

    Astro is a web framework. Prior to version 9.5.4, Server-Side Rendered pages that return an error with a prerendered custom error page (eg. `404.astro` or `500.astro`) are vulnerable to SSRF. If the `Host:` header is changed to an attacker's server, it will be fetched on `/500.html` and they can redirect this to any internal URL to read the response body through the first request. An attacker who can access the application without `Host:` header validation (eg. through finding the origin IP behind a proxy, or just by default) can fetch their own server to redirect to any internal IP. With this they can fetch cloud metadata IPs and interact wi

    • Mettez à jour vers 9.5.4
    Publication Mise à jour
  3. CVE-2025-69985

    Critique · CVSS 9.8EPSS 5,97%Code d’exploitation publicAucun correctif publié

    CVE-2025-69985

    FUXA 1.2.8 and prior contains an Authentication Bypass vulnerability leading to Remote Code Execution (RCE). The vulnerability exists in the server/api/jwt-helper.js middleware, which improperly trusts the HTTP "Referer" header to validate internal requests. A remote unauthenticated attacker can bypass JWT authentication by spoofing the Referer header to match the server's host. Successful exploitation allows the attacker to access the protected /api/runscript endpoint and execute arbitrary Node.js code on the server.

    Publication Mise à jour
  4. CVE-2025-70058

    Élevée · CVSS 7.4EPSS 0,19%Aucun correctif publié

    CVE-2025-70058

    An issue pertaining to CWE-295: Improper Certificate Validation was discovered in YMFE yapi v1.12.0. The application disables TLS/SSL certificate validation by setting 'rejectUnauthorized': false in the HTTPS agent configuration for Axios requests

    Publication Mise à jour
  5. CVE-2026-27492

    Moyenne · CVSS 4.7EPSS 0,19%Correctif disponible

    Lettermint Node.js SDK leaks email properties to unintended recipients when client instance is reused

    Lettermint Node.js SDK is the official Node.js SDK for Lettermint. In versions 1.5.0 and below, email properties (such as to, subject, html, text, and attachments) are not reset between sends when a single client instance is reused across multiple .send() calls. This can cause properties from a previous send to leak into a subsequent one, potentially delivering content or recipient addresses to unintended parties. Applications sending emails to different recipients in sequence — such as transactional flows like password resets or notifications — are affected. This issue has been fixed in version 1.5.1.

    • Mettez à jour vers 1.5.1
    Publication Mise à jour
  6. CVE-2026-27574

    Critique · CVSS 10EPSS 0,56%Correctif disponible

    OneUptime: node:vm sandbox escape in probe allows any project member to achieve RCE

    OneUptime is a solution for monitoring and managing online services. In versions 9.5.13 and below, custom JavaScript monitor feature uses Node.js's node:vm module (explicitly documented as not a security mechanism) to execute user-supplied code, allowing trivial sandbox escape via a well-known one-liner that grants full access to the underlying process. Because the probe runs with host networking and holds all cluster credentials (ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD) in its environment variables, and monitor creation is available to the lowest role (ProjectMember) with open registration enabled by default,

    • Mettez à jour vers 10.0.0
    Publication Mise à jour
  7. CVE-2026-27576

    Moyenne · CVSS 4.8EPSS 0,18%Correctif disponible

    OpenClaw: ACP prompt-size checks missing in local stdio bridge could reduce responsiveness with very large inputs

    OpenClaw is a personal AI assistant. In versions 2026.2.17 and below, the ACP bridge accepts very large prompt text blocks and can assemble oversized prompt payloads before forwarding them to chat.send. Because ACP runs over local stdio, this mainly affects local ACP clients (for example IDE integrations) that send unusually large inputs. This issue has been fixed in version 2026.2.19.

    • Mettez à jour vers 2026.2.19
    Publication Mise à jour
  8. CVE-2026-27488

    Moyenne · CVSS 6.9EPSS 0,37%Correctif disponible

    OpenClaw hardened cron webhook delivery against SSRF

    OpenClaw is a personal AI assistant. In versions 2026.2.17 and below, Cron webhook delivery in src/gateway/server-cron.ts uses fetch() directly, so webhook targets can reach private/metadata/internal endpoints without SSRF policy checks. This issue was fixed in version 2026.2.19.

    • Mettez à jour vers 2026.2.19
    Publication Mise à jour
  9. CVE-2026-27487

    Élevée · CVSS 7.6EPSS 1,37%Correctif disponible

    OpenClaw: Prevent shell injection in macOS keychain credential write

    OpenClaw is a personal AI assistant. In versions 2026.2.13 and below, when using macOS, the Claude CLI keychain credential refresh path constructed a shell command to write the updated JSON blob into Keychain via security add-generic-password -w .... Because OAuth tokens are user-controlled data, this created an OS command injection risk. This issue has been fixed in version 2026.2.14.

    • Mettez à jour vers 2026.2.14
    Publication Mise à jour
  10. CVE-2026-27486

    Moyenne · CVSS 4.3EPSS 0,32%Correctif disponible

    OpenClaw: Process Safety - Unvalidated PID Kill via SIGKILL in Process Cleanup

    OpenClaw is a personal AI assistant. In versions 2026.2.13 and below of the OpenClaw CLI, the process cleanup uses system-wide process enumeration and pattern matching to terminate processes without verifying if they are owned by the current OpenClaw process. On shared hosts, unrelated processes can be terminated if they match the pattern. The CLI runner cleanup helpers can kill processes matched by command-line patterns without validating process ownership. This issue has been fixed in version 2026.2.14.

    • Mettez à jour vers 2026.2.14
    Publication Mise à jour
  11. CVE-2026-27485

    Moyenne · CVSS 4.6EPSS 0,25%Correctif disponible

    OpenClaw affected by Stored XSS in Control UI via unsanitized assistant name/avatar in inline script injection

    OpenClaw is a personal AI assistant. In versions 2026.2.17 and below, skills/skill-creator/scripts/package_skill.py (a local helper script used when authors package skills) previously followed symlinks while building .skill archives. If an author runs this script on a crafted local skill directory containing symlinks to files outside the skill root, the resulting archive can include unintended file contents. If exploited, this vulnerability can lead to potential unintentional disclosure of local files from the packaging machine into a generated .skill artifact, but requires local execution of the packaging script on attacker-controlled skill

    • Mettez à jour vers 2026.2.19
    Publication Mise à jour
  12. CVE-2026-27484

    Faible · CVSS 2.3EPSS 0,22%Correctif disponible

    OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows

    OpenClaw is a personal AI assistant. In versions 2026.2.17 and below, the Discord moderation action handling (timeout, kick, ban) uses sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context. In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user can request moderation actions by spoofing sender identity fields. This issue has been fixed in version 2026.2.18.

    • Mettez à jour vers 2026.2.18
    Publication Mise à jour
  13. CVE-2026-27212

    Critique · CVSS 9.4EPSS 0,49%Correctif disponible

    Swiper has a Prototype Pollution Vulnerability

    Swiper is a free and mobile touch slider with hardware accelerated transitions and native behavior. Versions 6.5.1 through 12.1.1 have a Prototype pollution vulnerability. The vulnerability resides in line 94 of shared/utils.mjs, where the indexOf() function is used to check whether user provided input contain forbidden strings. Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using Array.prototype. The exploit works across Windows and Linux and on Node and Bun runtimes. Any application that proc

    • Mettez à jour vers 12.1.2
    Publication Mise à jour
  14. CVE-2026-27210

    Moyenne · CVSS 5.3EPSS 0,37%Correctif disponible

    Pannellum has a XSS vulnerability in hot spot attributes

    Pannellum is a lightweight, free, and open source panorama viewer for the web. In versions 3.5.0 through 2.5.6, the hot spot attributes configuration property allowed any attribute to be set, including HTML event handler attributes, allowing for potential XSS attacks. This affects websites hosting the standalone viewer HTML file and any other use of untrusted JSON config files (bypassing the protections of the escapeHTML parameter). As certain events fire without any additional user interaction, visiting a standalone viewer URL that points to a malicious config file — without additional user interaction — is sufficient to trigger the vulnerab

    • Mettez à jour vers 2.5.7
    Publication Mise à jour
  15. CVE-2026-27193

    Élevée · CVSS 8.2EPSS 0,4%Correctif disponible

    Feathers exposes internal headers via unencrypted session cookie

    Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. In versions 5.0.39 and below, all HTTP request headers are stored in the session cookie, which is signed but not encrypted, exposing internal proxy/gateway headers to clients. The OAuth service stores the complete headers object in the session, then the session is persisted using cookie-session, which base64-encodes the data. While the cookie is signed to prevent tampering, the contents are readable by anyone by simply decoding the base64 value. Under specific deployment configurations (e.g., behind reverse proxies or API gateways), this

    • Mettez à jour vers 5.0.40
    Publication Mise à jour
  16. CVE-2026-27192

    Élevée · CVSS 7.6EPSS 0,27%Correctif disponible

    Feathers has an origin validation bypass via prefix matching

    Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. In versions 5.0.39 and below, origin validation uses startsWith() for comparison, allowing attackers to bypass the check by registering a domain that shares a common prefix with an allowed origin.The getAllowedOrigin() function checks if the Referer header starts with any allowed origin, and this comparison is insufficient as it only validates the prefix. This is exploitable when the origins array is configured and an attacker registers a domain starting with an allowed origin string (e.g., https://target.com.attacker.com bypasses https:/

    • Mettez à jour vers 5.0.40
    Publication Mise à jour
  17. CVE-2026-27191

    Élevée · CVSS 7.4EPSS 0,29%Correctif disponible

    Feathers: Open Redirect in OAuth callback enables account takeover

    Feathersjs is a framework for creating web APIs and real-time applications with TypeScript or JavaScript. Versions 5.0.39 and below the redirect query parameter is appended to the base origin without validation, allowing attackers to steal access tokens via URL authority injection. This leads to full account takeover, as the attacker obtains the victim's access token and can impersonate them. The application constructs the final redirect URL by concatenating the base origin with the user-supplied redirect parameter. This is exploitable when the origins array is configured and origin values do not end with /. An attacker can supply @attacker.c

    • Mettez à jour vers 5.0.40
    Publication Mise à jour
  18. CVE-2026-27203

    Élevée · CVSS 8.3EPSS 0,4%Aucun correctif publié

    eBay API MCP Server Affected by Environment Variable Injection

    eBay API MCP Server is an open source local MCP server providing AI assistants with comprehensive access to eBay's Sell APIs. All versions are vulnerable to Environment Variable Injection through the updateEnvFile function. The ebay_set_user_tokens tool allows updating the .env file with new tokens. The updateEnvFile function in src/auth/oauth.ts blindly appends or replaces values without validating them for newlines or quotes. This allows an attacker to inject arbitrary environment variables into the configuration file. An attacker can inject arbitrary environment variables into the .env file. This could lead to configuration overwrites, Den

    Publication Mise à jour
  19. CVE-2026-27125

    Moyenne · CVSS 5.3EPSS 0,43%Correctif disponible

    Svelte SSR attribute spreading includes inherited properties from prototype chain

    svelte performance oriented web framework. Prior to 5.51.5, in server-side rendering, attribute spreading on elements (e.g. <div {...attrs}>) enumerates inherited properties from the object's prototype chain rather than only own properties. In environments where Object.prototype has already been polluted — a precondition outside of Svelte's control — this can cause unexpected attributes to appear in SSR output or cause SSR to throw errors. Client-side rendering is not affected. This vulnerability is fixed in 5.51.5.

    • Mettez à jour vers 5.51.5
    Publication Mise à jour
  20. CVE-2026-27122

    Moyenne · CVSS 5.1EPSS 0,22%Correctif disponible

    Svelte SSR does not validate dynamic element tag names in `<svelte:element>`

    svelte performance oriented web framework. Prior to 5.51.5, when using <svelte:element this={tag}> in server-side rendering, the provided tag name is not validated or sanitized before being emitted into the HTML output. If the tag string contains unexpected characters, it can result in HTML injection in the SSR output. Client-side rendering is not affected. This vulnerability is fixed in 5.51.5.

    • Mettez à jour vers 5.51.5
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →