How severe is GHSA-8r4g-cg4m-x23c?

No CVSS score has been assigned to GHSA-8r4g-cg4m-x23c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8r4g-cg4m-x23c?

GHSA-8r4g-cg4m-x23c affects the following packages: node-static (npm). Ecosystems affected: npm.

How do I fix GHSA-8r4g-cg4m-x23c?

No patched version of node-static has shipped for GHSA-8r4g-cg4m-x23c yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-8r4g-cg4m-x23c in my npm dependencies?

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

How do I mitigate GHSA-8r4g-cg4m-x23c 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-8r4g-cg4m-x23c actively exploited in the wild?

No public exploit code has been indexed for GHSA-8r4g-cg4m-x23c 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-8r4g-cg4m-x23c published, and has it been updated?

GHSA-8r4g-cg4m-x23c was published on September 22, 2021 and was last updated on October 3, 2025. 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

Denial of Service in node-staticGHSA-8r4g-cg4m-x23c

Fix: cloudhead/node-static#213

GHSA-8r4g-cg4m-x23c is a security vulnerability in node-static. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 22, 2021

Updated

Oct 3, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 3, 2025 · OSV.dev, FIRST.org (EPSS)

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.

469other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

node-staticnpm

61Kdownloads / week

Description

All versions of node-static are vulnerable to a Denial of Service. The package fails to catch an exception when user input includes null bytes. This allows attackers to access http://host/%00 and crash the server.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-static`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-static, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of node-static has shipped for GHSA-8r4g-cg4m-x23c yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 node-static are vulnerable to a Denial of Service. The package fails to catch an exception when user input includes null bytes. This allows attackers to access `http://host/%00` and crash the server.

O3 Security · Impact-Aware SCA

Is GHSA-8r4g-cg4m-x23c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works