{"id":"CVE-2026-104844","aliases":["CLSA-2026-1791278836","CLSA-2026-1792450509","CLSA-2026-1792473324","CLSA-2026-1792476079","CLSA-2026-1792489723","CLSA-2026-1792489741","CLSA-2026-1792489830","CLSA-2026-1792489937","EUVD-2026-91741","GHSA-rj75-hqrm-r3gf","openSUSE-SU-2026:12083-1"],"status":"published","title":"PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion","description":"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 maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00389,"percentile":0.33465,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-400","CWE-407"],"published":"2026-10-02T15:43:14Z","modified":"2026-10-28T02:31:12Z","fixes":[{"ecosystem":"npm","package":"postcss-selector-parser","fixed_in":["7.1.6","6.1.5"],"sources":["ghsa","osv"]},{"ecosystem":"TuxCare:npm","package":"postcss-selector-parser","fixed_in":["3.1.2-tuxcare.1","2.2.3-tuxcare.1","5.0.0-tuxcare.1","6.1.4-tuxcare.1","7.1.4-tuxcare.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"git-bug","fixed_in":["0.11.0-2.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.0"},{"fixed":"7.1.6"}]}]},{"source":"ghsa","ecosystem":"npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.5"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.1.2-tuxcare.0"},{"fixed":"3.1.2-tuxcare.1"}]}],"versions":["3.1.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.1.0-tuxcare.0"},{"fixed":"7.1.0-tuxcare.1"}]}],"versions":["7.1.0"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.2.3-tuxcare.0"},{"fixed":"2.2.3-tuxcare.1"}]}],"versions":["2.2.3"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.2-tuxcare.0"},{"fixed":"6.1.2-tuxcare.1"}]}],"versions":["6.1.2"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0-tuxcare.0"},{"fixed":"5.0.0-tuxcare.1"}]}],"versions":["5.0.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.4-tuxcare.0"},{"fixed":"6.1.4-tuxcare.1"}]}],"versions":["6.1.4"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.1.4-tuxcare.0"},{"fixed":"7.1.4-tuxcare.1"}]}],"versions":["7.1.4"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"postcss-selector-parser","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.1.1-tuxcare.0"},{"fixed":"7.1.1-tuxcare.1"}]}],"versions":["7.1.1"],"bundled":2},{"source":"osv","ecosystem":"npm","package":"postcss-selector-parser","ranges":[{"type":"SEMVER","events":[{"introduced":"7.0.0"},{"fixed":"7.1.6"}]}]},{"source":"osv","ecosystem":"npm","package":"postcss-selector-parser","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.1.5"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"git-bug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.0-2.1"}]}]}],"products":[{"vendor":"postcss","product":"postcss-selector-parser"}],"references":[{"url":"https://github.com/postcss/postcss-selector-parser/security/advisories/GHSA-rj75-hqrm-r3gf","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/postcss/postcss-selector-parser/commit/62b191792df0a0bc56062e5a875bc74aae2a51cd","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/postcss/postcss-selector-parser/releases/tag/7.1.6","tags":["x_refsource_MISC","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-104844","tags":["advisory"]},{"url":"https://github.com/postcss/postcss-selector-parser/pull/346","tags":["web"]},{"url":"https://github.com/postcss/postcss-selector-parser/commit/70b0779c843462197380d25daa02d1528bf7eae5","tags":["web"]},{"url":"https://github.com/postcss/postcss-selector-parser/releases/tag/6.1.5","tags":["web"]},{"url":"https://github.com/advisories/GHSA-rj75-hqrm-r3gf"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104844.json","tags":["advisory"]},{"url":"https://github.com/postcss/postcss-selector-parser","tags":["package"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-104844","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-104844","title":"PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion","description":"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 maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.","status":"published","published":"2026-10-02T15:43:14.082Z","modified":"2026-10-02T16:16:45.99Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-400","CWE-407"],"updated_at":"2026-11-02T14:20:09.098623Z"}],"euvd":[{"id":"EUVD-2026-91741","description":"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 maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.","status":"published","published":"2026-10-02T15:43:14Z","modified":"2026-10-02T16:16:45Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T17:27:42.693498Z"}],"ghsa":[{"id":"GHSA-rj75-hqrm-r3gf","title":"PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion","description":"### Impact\n\n`.` and `#` are not word delimiters in the tokenizer, so a flat selector such as\n`.a.a.a...` reaches `splitWord()` as a single word token carrying n class or id\nindexes. Three passes scanned those index arrays linearly for every index,\nmaking the parse O(n^2) in the number of indexes rather than in input length:\n`uniqs()`, the `indices.forEach` loop, and the Sass-interpolation filter.\nParsing a 400 KB flat selector took ~34 s on a modern laptop, fully occupying a\nsingle thread. A benign selector of identical byte size parses in tens of\nmilliseconds, so the cost is driven by the index count, not the input size.\nThe nesting depth of such a selector is 0, so the `maxNestingDepth` guard added\nin 7.1.3 offers no protection.\n\nReachability is deployment dependent. Only consumers that parse untrusted,\nattacker-supplied selectors synchronously in a request path are exposed, for\nexample CSS sanitizers, CSS-in-JS services and online playgrounds. Ordinary\nbuild-time use on trusted sources is not affected.\n\n### Patches\n\nFixed in 7.1.6. The three passes now use Set membership tests, making parsing\nlinear in the number of indexes. There is no behaviour change: parsing is\nbyte-identical on a differential corpus of 8413 selectors.\n\n### Workarounds\n\nCap the size of selectors accepted from untrusted sources before parsing.","status":"published","published":"2026-10-05T22:53:54Z","modified":"2026-10-26T14:07:57Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-400","CWE-407"],"updated_at":"2026-11-02T14:41:36.858527Z"}],"nvd":[{"id":"CVE-2026-104844","description":"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 maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.","status":"published","published":"2026-10-02T16:16:46.917Z","modified":"2026-10-02T18:44:11.27Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"}],"cwes":["CWE-400","CWE-407"],"updated_at":"2026-11-02T14:12:53.75133Z"}],"osv":[{"id":"CVE-2026-104844","title":"PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion","description":"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 maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.","status":"published","published":"2026-10-02T15:43:14.082Z","modified":"2026-10-28T02:31:12.415082975Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-400","CWE-407"],"updated_at":"2026-11-02T15:44:54.236592Z"},{"id":"GHSA-rj75-hqrm-r3gf","title":"PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion","description":"### Impact\n\n`.` and `#` are not word delimiters in the tokenizer, so a flat selector such as\n`.a.a.a...` reaches `splitWord()` as a single word token carrying n class or id\nindexes. Three passes scanned those index arrays linearly for every index,\nmaking the parse O(n^2) in the number of indexes rather than in input length:\n`uniqs()`, the `indices.forEach` loop, and the Sass-interpolation filter.\nParsing a 400 KB flat selector took ~34 s on a modern laptop, fully occupying a\nsingle thread. A benign selector of identical byte size parses in tens of\nmilliseconds, so the cost is driven by the index count, not the input size.\nThe nesting depth of such a selector is 0, so the `maxNestingDepth` guard added\nin 7.1.3 offers no protection.\n\nReachability is deployment dependent. Only consumers that parse untrusted,\nattacker-supplied selectors synchronously in a request path are exposed, for\nexample CSS sanitizers, CSS-in-JS services and online playgrounds. Ordinary\nbuild-time use on trusted sources is not affected.\n\n### Patches\n\nFixed in 7.1.6. The three passes now use Set membership tests, making parsing\nlinear in the number of indexes. There is no behaviour change: parsing is\nbyte-identical on a differential corpus of 8413 selectors.\n\n### Workarounds\n\nCap the size of selectors accepted from untrusted sources before parsing.","status":"published","published":"2026-10-05T22:53:54Z","modified":"2026-10-26T14:16:59.921540799Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-400","CWE-407"],"updated_at":"2026-11-02T15:46:55.877614Z"},{"id":"CLSA-2026-1791278836","title":"TuxCare security update for postcss-selector-parser (1 CVE)","description":"TuxCare rebuilt postcss-selector-parser to address 1 CVE. Fixed in 3.1.2-tuxcare.1.","status":"published","published":"2026-10-06T09:27:16Z","modified":"2026-10-15T09:47:35.587189663Z","updated_at":"2026-11-02T15:43:49.016976Z"},{"id":"CLSA-2026-1792450509","title":"TuxCare security update for postcss-selector-parser (2 CVEs)","description":"TuxCare rebuilt postcss-selector-parser to address 2 CVEs. Fixed in 7.1.0-tuxcare.1.","status":"published","published":"2026-10-19T22:55:09Z","modified":"2026-10-20T01:45:18.558005354Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"CLSA-2026-1792473324","title":"TuxCare security update for postcss-selector-parser (1 CVE)","description":"TuxCare rebuilt postcss-selector-parser to address 1 CVE. Fixed in 2.2.3-tuxcare.1.","status":"published","published":"2026-10-20T05:15:24Z","modified":"2026-10-20T07:15:16.14361892Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"CLSA-2026-1792476079","title":"TuxCare security update for postcss-selector-parser (2 CVEs)","description":"TuxCare rebuilt postcss-selector-parser to address 2 CVEs. Fixed in 6.1.2-tuxcare.1.","status":"published","published":"2026-10-20T06:01:19Z","modified":"2026-10-20T07:15:15.377528464Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"CLSA-2026-1792489723","title":"TuxCare security update for postcss-selector-parser (1 CVE)","description":"TuxCare rebuilt postcss-selector-parser to address 1 CVE. Fixed in 5.0.0-tuxcare.1.","status":"published","published":"2026-10-20T09:48:43Z","modified":"2026-10-20T13:45:12.466280168Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"CLSA-2026-1792489741","title":"TuxCare security update for postcss-selector-parser (1 CVE)","description":"TuxCare rebuilt postcss-selector-parser to address 1 CVE. Fixed in 6.1.4-tuxcare.1.","status":"published","published":"2026-10-20T09:49:01Z","modified":"2026-10-20T13:45:16.02263456Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"CLSA-2026-1792489830","title":"TuxCare security update for postcss-selector-parser (1 CVE)","description":"TuxCare rebuilt postcss-selector-parser to address 1 CVE. Fixed in 7.1.4-tuxcare.1.","status":"published","published":"2026-10-20T09:50:30Z","modified":"2026-10-20T13:45:11.469677077Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"CLSA-2026-1792489937","title":"TuxCare security update for postcss-selector-parser (2 CVEs)","description":"TuxCare rebuilt postcss-selector-parser to address 2 CVEs. Fixed in 7.1.1-tuxcare.1.","status":"published","published":"2026-10-20T09:52:17Z","modified":"2026-10-20T13:45:16.017581597Z","updated_at":"2026-11-02T15:43:54.378946Z"},{"id":"openSUSE-SU-2026:12083-1","title":"git-bug-0.11.0-2.1 on GA media","description":"These are all security issues fixed in the git-bug-0.11.0-2.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-10-08T00:00:00Z","modified":"2026-10-09T17:23:13.620211326Z","updated_at":"2026-11-02T16:58:40.245664Z"}]}}