p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in node-multiparty

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für node-multiparty: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4

  1. CVE-2026-87908

    Hoch · CVSS 7.5EPSS 0,51%Korrektur verfügbar

    multiparty vulnerable to Denial of Service via unbounded part-header accumulation

    multiparty is a Node.js library for parsing multipart/form-data request bodies. In versions from 2.1.0 up to but not including 4.3.1, the parser does not bound the amount of memory used while accumulating the headers of a single multipart part. An unauthenticated attacker can send a single request whose part carries a very large volume of header bytes, forcing the parser to buffer all of them and exhausting the process memory, which crashes the server. This is a denial of service with no confidentiality or integrity impact. The issue is fixed in multiparty 4.3.1, which caps the size of the accumulated part headers. Users should upgrade to mul

    • Auf 4.3.1+~4.2.1-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-8162

    Hoch · CVSS 7.5EPSS 0,33%Korrektur verfügbar

    multiparty vulnerable to Denial of Service via Uncaught Exception in filename* parameter parsing

    [email protected] and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a Content-Disposition header whose filename* parameter contains a malformed percent-encoding, the parser invokes decodeURI on the value without try/catch. The resulting URIError propagates as an uncaught exception and crashes the process. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: none. Upgrade to [email protected] or higher.

    • Auf 4.3.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-8161

    Hoch · CVSS 7.5EPSS 0,47%Korrektur verfügbar

    multiparty vulnerable to Denial of Service via Prototype Pollution leading to Uncaught Exception

    [email protected] and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a field name that collides with an inherited Object.prototype property such as __proto__, constructor, or toString, the parser invokes .push() on the inherited prototype value rather than an array, throwing a TypeError that propagates as an uncaught exception and crashes the process. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: none. Upgrade to [email protected] or higher.

    • Auf 4.3.0-1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-8159

    Hoch · CVSS 7.5EPSS 0,34%Korrektur verfügbar

    multiparty vulnerable to ReDoS via filename parsing

    [email protected] and lower versions are vulnerable to denial of service via regular expression backtracking in the Content-Disposition filename parameter parser. A crafted multipart upload with a long header value can cause regex matching to take seconds, blocking the event loop. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: limiting upload sizes at the proxy or gateway layer reduces but does not eliminate the attack surface, since a small header of around 8 KB is sufficient to trigger the vulnerable backtracking. Upgrade to [email protected] or higher.

    • Auf 4.3.0-1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →