How severe is GHSA-cv3v-7846-6pxm?

GHSA-cv3v-7846-6pxm has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cv3v-7846-6pxm?

GHSA-cv3v-7846-6pxm affects the following packages: node-git-server (npm). Ecosystems affected: npm.

How do I fix GHSA-cv3v-7846-6pxm?

Update node-git-server to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv3v-7846-6pxm is resolved across your whole dependency graph.

How do I detect GHSA-cv3v-7846-6pxm in my npm dependencies?

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

How do I mitigate GHSA-cv3v-7846-6pxm 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.

Is GHSA-cv3v-7846-6pxm actively exploited in the wild?

No public exploit code has been indexed for GHSA-cv3v-7846-6pxm 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-cv3v-7846-6pxm published, and has it been updated?

GHSA-cv3v-7846-6pxm was published on September 3, 2020 and was last updated on July 17, 2026. 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

HIGH severity

Unauthorized File Access in node-git-serverGHSA-cv3v-7846-6pxm

HIGHFix: gabrielcsapo/node-git-server#62

GHSA-cv3v-7846-6pxm is a high-severity (CVSS 7.5) vulnerability in node-git-server. A fix is available for node-git-server — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Jul 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 17, 2026 · 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.

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

node-git-servernpm

27Kdownloads / week

Description

Versions of node-git-server prior to 0.6.1 are vulnerable to Unauthorized File Access. It is possible to access any git repository by using absolute paths, which may allow attackers to access private repositories.

Recommendation

Upgrade to version 0.6.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-git-server`	≥ 0.2.0&&< 0.6.1	0.6.1`npm install node-git-server@0.6.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-git-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update node-git-server to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv3v-7846-6pxm 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.

Frequently Asked Questions

Versions of `node-git-server` prior to 0.6.1 are vulnerable to Unauthorized File Access. It is possible to access any git repository by using absolute paths, which may allow attackers to access private repositories. ## Recommendation Upgrade to version 0.6.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-cv3v-7846-6pxm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works