Repository navigation
chore(deps): update dependency postcss-selector-parser to v6.1.5 [security] - #1961
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
✅ Deploy Preview for compiled-css-in-js canceled.
|
|
renovate
Bot
force-pushed
the
renovate/npm-postcss-selector-parser-vulnerability
branch
2 times, most recently
from
October 21, 2026 02:38
4a70117 to
12d2d86
Compare
renovate
Bot
deleted the
renovate/npm-postcss-selector-parser-vulnerability
branch
October 26, 2026 14:32
renovate
Bot
force-pushed
the
renovate/npm-postcss-selector-parser-vulnerability
branch
from
November 1, 2026 05:10
12d2d86 to
65d1b38
Compare
renovate
Bot
force-pushed
the
renovate/npm-postcss-selector-parser-vulnerability
branch
from
November 10, 2026 02:01
65d1b38 to
8fe3609
Compare
renovate
Bot
force-pushed
the
renovate/npm-postcss-selector-parser-vulnerability
branch
3 times, most recently
from
November 16, 2026 01:18
8672244 to
eb6222a
Compare
renovate
Bot
force-pushed
the
renovate/npm-postcss-selector-parser-vulnerability
branch
from
November 16, 2026 01:45
eb6222a to
e10cf55
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.0.13→6.1.5PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion
CVE-2026-104844 / GHSA-rj75-hqrm-r3gf
More information
Details
Impact
.and#are not word delimiters in the tokenizer, so a flat selector such as.a.a.a...reachessplitWord()as a single word token carrying n class or idindexes. Three passes scanned those index arrays linearly for every index,
making the parse O(n^2) in the number of indexes rather than in input length:
uniqs(), theindices.forEachloop, and the Sass-interpolation filter.Parsing a 400 KB flat selector took ~34 s on a modern laptop, fully occupying a
single thread. A benign selector of identical byte size parses in tens of
milliseconds, so the cost is driven by the index count, not the input size.
The nesting depth of such a selector is 0, so the
maxNestingDepthguard addedin 7.1.3 offers no protection.
Reachability is deployment dependent. Only consumers that parse untrusted,
attacker-supplied selectors synchronously in a request path are exposed, for
example CSS sanitizers, CSS-in-JS services and online playgrounds. Ordinary
build-time use on trusted sources is not affected.
Patches
Fixed in 7.1.6. The three passes now use Set membership tests, making parsing
linear in the number of indexes. There is no behaviour change: parsing is
byte-identical on a differential corpus of 8413 selectors.
Workarounds
Cap the size of selectors accepted from untrusted sources before parsing.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
postcss/postcss-selector-parser (postcss-selector-parser)
v6.1.5Compare Source
The 6.x line is now in security-only maintenance
This release exists because the advisory above covers every published 6.x
version, and until now the only remediation on offer was an upgrade to 7.x.
6.1.5 is the patched version for the 6.x line.
The line is kept alive for the installed base that cannot move to 7 yet, Tailwind
CSS 3 in particular, which depends on
^6.1.2. From here on it receives securityfixes only: no features, no other bug fixes, no type changes. Everything else
goes to 7.x, where this package is actively developed. Tailwind CSS 4 no longer
depends on this package at all, so this line is expected to retire on its own.
6.1.5 is published under the
legacy-v6npm dist-tag, sonpm install postcss-selector-parserkeeps resolving to 7.x. Existing^6ranges pick up 6.1.5 as usual.
v6.1.4Compare Source
v6.1.3Compare Source
v6.1.2Compare Source
v6.1.1Compare Source
v6.1.0Compare Source
sourceIndextoSelectornodes (#290)v6.0.16Compare Source
indexargument toeach/walkcallback types (#289)v6.0.15Compare Source
v6.0.14Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.