Is postcss-selector-parser 1.3 vulnerable?
npm · 4 releases from 1.3.0 to 1.3.3 · latest postcss-selector-parser is 7.1.7 · checked 2 Nov 2026
Yes: 1 known advisory
Yes. postcss-selector-parser 1.3.3, the last 1.3 release, is affected by 1 known security advisory (1 medium), including CVE-2026-104844. Upgrade to 6.1.5 or later to fix all of them.
Upgrade with:
npm install postcss-selector-parser@6.1.5Advisories affecting postcss-selector-parser 1.3.3
PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion
- Affected
- >=7.0.0 <7.1.6 · <6.1.5
- Fixed in
- 6.1.5, 7.1.6
Which of your client projects are still on postcss-selector-parser 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact postcss-selector-parser version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other postcss-selector-parser versions
- postcss-selector-parser 2.2
- postcss-selector-parser 2.1
- postcss-selector-parser 2.0
- postcss-selector-parser 1.2
- postcss-selector-parser 1.1
- postcss-selector-parser 1.0
- postcss-selector-parser 7.1
- postcss-selector-parser 7.0
- postcss-selector-parser 6.1
- postcss-selector-parser 6.0
- postcss-selector-parser 5.0
- All postcss-selector-parser advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.