NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2021-33587 — css-what

HIGHFix: fb55/css-what@4cdaacf

CVE-2021-33587 is a high-severity (CVSS 7.5) vulnerability in css-what. A fix is available for css-what — see the affected versions and patch details below.

Denial of service in css-what

Also known asGHSA-q8pj-2vqx-8ggc
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
0.00%0.96%1.93%2.89%0.2%2.0%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

731other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
css-whatnpm
106.1Mdownloads / week

Description

The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmcss-what≥ 4.0.0&&< 5.0.15.0.1npm install css-what@5.0.1

Affected Products

2 products · 3 configurations
Application
css-whatcss-what_project
2 versions
4.0.05.0.0
Application
e-series performance analyzernetapp
all

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for css-what, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update css-what to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-33587 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input.
O3 Security · Impact-Aware SCA

Is CVE-2021-33587 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2021-33587: css-what — Fixed in 5.0.1