p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in postcss-selector-parser

In den letzten 30 Tagen veröffentlichte Sicherheitslücke für postcss-selector-parser: 1. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2026-104844

    Mittel · CVSS 5.9EPSS 0,39%Korrektur verfügbar

    PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion

    PostCSS Selector Parser is a CSS selector parser that integrates with PostCSS but does not require it. Prior to 7.1.6, src/parser.js splitWord() can receive a flat selector as one word token carrying many class or ID indexes because period and hash characters are not tokenizer word delimiters. The uniqs() deduplication and per-index class and ID membership checks repeatedly scan the class and ID index arrays, while a separate Sass-interpolation filtering pass also performs repeated linear scanning. Together, these passes make parsing quadratic in the number of indexes and allow a crafted selector to occupy a synchronous parser thread. The max

    • Auf 6.1.5 aktualisieren
    • Auf 7.1.6 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-9358

    Mittel · CVSS 5.3EPSS 0,33%Korrektur verfügbar

    postcss-selector-parser AST Serialization container.js toString recursion

    A vulnerability was determined in postcss-selector-parser up to 6.1.2/7.1.2. Affected is the function toString of the file src/selectors/container.js of the component AST Serialization. Executing a manipulation can lead to uncontrolled recursion. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 6.1.3 and 7.1.3 is able to address this issue. This patch is called 5bc698cef66f8abd12610dc623e5d67cbc0f869d. It is suggested to upgrade the affected component. The vendor explains, that according to his definition "DoS on server-side on user-generated CSS is low risk for us

    • Auf 6.1.3 aktualisieren
    • Auf 7.1.3 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 →