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

CVE-2022-25758 — scss-tokenizer

HIGHFix: sasstools/scss-tokenizer#49

CVE-2022-25758 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in scss-tokenizer. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for scss-tokenizer — see the affected versions and patch details below.

Regular expression denial of service in scss-tokenizer

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
3 known
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk
0.00%0.88%1.76%2.64%0.5%2.1%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.

35other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
scss-tokenizernpm
796Kdownloads / week

Description

All versions of the package scss-tokenizer prior to 0.4.3 are vulnerable to Regular Expression Denial of Service (ReDoS) via the loadAnnotation() function, due to the usage of insecure regex.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmscss-tokenizerall versions0.4.3npm install scss-tokenizer@0.4.3

Affected Products

1 product · 1 configurations
Application
scss-tokenizerscss-tokenizer_project
all
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update scss-tokenizer to 0.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25758 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

All versions of the package `scss-tokenizer` prior to 0.4.3 are vulnerable to Regular Expression Denial of Service (ReDoS) via the `loadAnnotation()` function, due to the usage of insecure regex.
O3 Security · Impact-Aware SCA

Is CVE-2022-25758 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-25758: scss-tokenizer DoS — Fixed in 0.4.3