How severe is GHSA-qjfh-xc44-rm9x?

No CVSS score has been assigned to GHSA-qjfh-xc44-rm9x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qjfh-xc44-rm9x?

GHSA-qjfh-xc44-rm9x affects the following packages: file-static-server (npm). Ecosystems affected: npm.

How do I fix GHSA-qjfh-xc44-rm9x?

No patched version of file-static-server has shipped for GHSA-qjfh-xc44-rm9x 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-qjfh-xc44-rm9x in my npm dependencies?

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

How do I mitigate GHSA-qjfh-xc44-rm9x if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-qjfh-xc44-rm9x actively exploited in the wild?

No public exploit code has been indexed for GHSA-qjfh-xc44-rm9x 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-qjfh-xc44-rm9x published, and has it been updated?

GHSA-qjfh-xc44-rm9x was published on September 3, 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.

📦 npm

Not in CISA KEV

Path Traversal in file-static-serverGHSA-qjfh-xc44-rm9x

GHSA-qjfh-xc44-rm9x is a security vulnerability in file-static-server. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

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

file-static-servernpm

26downloads / week

Description

All versions of file-static-server are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files.

Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`file-static-server`	≥ 0.0.0	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 file-static-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of file-static-server has shipped for GHSA-qjfh-xc44-rm9x 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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

All versions of `file-static-server` are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-qjfh-xc44-rm9x in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works