How severe is GHSA-48gc-5j93-5cfq?

No CVSS score has been assigned to GHSA-48gc-5j93-5cfq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-48gc-5j93-5cfq?

GHSA-48gc-5j93-5cfq affects the following packages: serve (npm). Ecosystems affected: npm.

How do I fix GHSA-48gc-5j93-5cfq?

Update serve to 10.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-48gc-5j93-5cfq is resolved across your whole dependency graph.

How do I detect GHSA-48gc-5j93-5cfq in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serve. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-48gc-5j93-5cfq if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-48gc-5j93-5cfq?

O3 pinpoints whether GHSA-48gc-5j93-5cfq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-48gc-5j93-5cfq actively exploited in the wild?

No public exploit code has been indexed for GHSA-48gc-5j93-5cfq 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-48gc-5j93-5cfq published, and has it been updated?

GHSA-48gc-5j93-5cfq was published on September 11, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-48gc-5j93-5cfq: Path Traversal in serve

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

servenpm

3.9Mdownloads / week

Description

Versions of serve prior to 10.1.2 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through relative paths, which allows attackers to access hidden folders and files.

Recommendation

Upgrade to version 10.1.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`serve`	all versions	10.1.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serve. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update serve to 10.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-48gc-5j93-5cfq is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-48gc-5j93-5cfq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-48gc-5j93-5cfq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `serve` prior to 10.1.2 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through relative paths, which allows attackers to access hidden folders and files. ## Recommendation Upgrade to version 10.1.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-48gc-5j93-5cfq in your dependencies?

O3 detects GHSA-48gc-5j93-5cfq across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-48gc-5j93-5cfq