Is postcss-selector-parser 6.0.10 vulnerable?

postcss-selector-parser 6.0.10, a JavaScript package on npm. All 4 versions we track · npm page

1 vulnerability

Upgrade postcss-selector-parser from 6.0.10 to 6.1.5 or later.

Known vulnerabilities in postcss-selector-parser 6.0.10

  • Medium CVSS 5.9

    CVE-2026-104844: PostCSS: Quadratic complexity in flat selector parsing allows CPU exhaustion

    GHSA-rj75-hqrm-r3gf · published 5 Oct 2026 · fixed in 6.1.5

How to fix it

With package-lock.json:

npm install postcss-selector-parser@6.1.5
# if it is an indirect dependency: npm update postcss-selector-parser (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the package's changelog for breaking changes (especially across major versions), update the lockfile with the package manager (never by hand), and run your tests.

Other versions of postcss-selector-parser

Newest version we track without known advisories: 7.2.1.

VersionKnown vulnerabilitiesHighest severity
7.2.1 0 None
6.1.6 0 None
6.1.0 2 Medium
6.0.10 (this page) 1 Medium

Every version of postcss-selector-parser →

Licence

postcss-selector-parser 6.0.10 declares MIT .

Check your whole project

postcss-selector-parser is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.

Get emailed about new advisories for postcss-selector-parser (free, no account)

About this data

Vulnerability data: OSV.dev, last checked 22 November 2026. Licence: deps.dev. AIssue checks the versions on this page every day. Severity comes from the advisory's own rating when it has one, else from its CVSS score.