How severe is GHSA-9v62-24cr-58cx?

GHSA-9v62-24cr-58cx has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-9v62-24cr-58cx?

GHSA-9v62-24cr-58cx affects the following packages: node-sass (npm). Ecosystems affected: npm.

How do I fix GHSA-9v62-24cr-58cx?

Update node-sass to 4.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9v62-24cr-58cx is resolved across your whole dependency graph.

How do I detect GHSA-9v62-24cr-58cx in my npm dependencies?

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

How do I mitigate GHSA-9v62-24cr-58cx if there is no patch (or I can't update yet)?

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.

Is GHSA-9v62-24cr-58cx actively exploited in the wild?

No public exploit code has been indexed for GHSA-9v62-24cr-58cx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9v62-24cr-58cx published, and has it been updated?

GHSA-9v62-24cr-58cx was published on September 11, 2020 and was last updated on September 28, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Denial of Service in node-sassGHSA-9v62-24cr-58cx

MEDIUMFix: sass/node-sass@338fd7a

GHSA-9v62-24cr-58cx is a medium-severity (CVSS 5.9) vulnerability in node-sass. A fix is available for node-sass — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Sep 28, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 28, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

node-sassnpm

1.1Mdownloads / week

Description

Affected versions of node-sass are vulnerable to Denial of Service (DoS). Crafted objects passed to the renderSync function may trigger C++ assertions in CustomImporterBridge::get_importer_entry and CustomImporterBridge::post_process_return_value that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service.

Recommendation

Upgrade to version 4.13.1 or later

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-sass`	≥ 3.3.0&&< 4.13.1	4.13.1`npm install node-sass@4.13.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-sass, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update node-sass to 4.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9v62-24cr-58cx is resolved across your whole dependency graph.
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

Affected versions of `node-sass` are vulnerable to Denial of Service (DoS). Crafted objects passed to the `renderSync` function may trigger C++ assertions in `CustomImporterBridge::get_importer_entry` and `CustomImporterBridge::post_process_return_value` that crash the Node process. This may allow attackers to crash the system's running Node process and lead to Denial of Service. ## Recommendation Upgrade to version 4.13.1 or later

O3 Security · Impact-Aware SCA

Is GHSA-9v62-24cr-58cx in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works