How severe is GHSA-v86x-f47q-f7f4?

No CVSS score has been assigned to GHSA-v86x-f47q-f7f4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v86x-f47q-f7f4?

GHSA-v86x-f47q-f7f4 affects the following packages: atompm (npm). Ecosystems affected: npm.

How do I fix GHSA-v86x-f47q-f7f4?

Update atompm to 0.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v86x-f47q-f7f4 is resolved across your whole dependency graph.

How do I detect GHSA-v86x-f47q-f7f4 in my npm dependencies?

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

How do I mitigate GHSA-v86x-f47q-f7f4 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-v86x-f47q-f7f4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v86x-f47q-f7f4 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-v86x-f47q-f7f4 published, and has it been updated?

GHSA-v86x-f47q-f7f4 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.

📦 npm

Not in CISA KEV

Unauthorized File Access in atompmGHSA-v86x-f47q-f7f4

GHSA-v86x-f47q-f7f4 is a security vulnerability in atompm. A fix is available for atompm — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

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

atompmnpm

7downloads / week

Description

Versions of atompm prior to 0.8.2 are vulnerable to Unauthorized File Access. The package fails to sanitize relative paths in the URL for file downloads, allowing attackers to download arbitrary files from the system.

Recommendation

Upgrade to version 0.8.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`atompm`	all versions	0.8.2`npm install atompm@0.8.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for atompm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update atompm to 0.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v86x-f47q-f7f4 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 `atompm` prior to 0.8.2 are vulnerable to Unauthorized File Access. The package fails to sanitize relative paths in the URL for file downloads, allowing attackers to download arbitrary files from the system. ## Recommendation Upgrade to version 0.8.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-v86x-f47q-f7f4 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works