How severe is GHSA-v6gv-fg46-h89j?

No CVSS score has been assigned to GHSA-v6gv-fg46-h89j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v6gv-fg46-h89j?

GHSA-v6gv-fg46-h89j affects the following packages: put (npm). Ecosystems affected: npm.

How do I fix GHSA-v6gv-fg46-h89j?

No patched version of put has shipped for GHSA-v6gv-fg46-h89j 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-v6gv-fg46-h89j in my npm dependencies?

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

How do I mitigate GHSA-v6gv-fg46-h89j 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-v6gv-fg46-h89j actively exploited in the wild?

No public exploit code has been indexed for GHSA-v6gv-fg46-h89j 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-v6gv-fg46-h89j published, and has it been updated?

GHSA-v6gv-fg46-h89j 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

Sensitive Data Exposure in putGHSA-v6gv-fg46-h89j

GHSA-v6gv-fg46-h89j is a security vulnerability in put. 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.

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

putnpm

7Kdownloads / week

Description

All versions of put are vulnerable to Uninitialized Memory Exposure. The package incorrectly calculates the allocated Buffer size and does not trim the bytes written, which may allow attackers to access uninitialized memory containing sensitive data. This vulnerability only affects versions of Node.js <=6.x.

Recommendation

Upgrade your Node.js version or consider using an alternative package.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`put`	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 put, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of put has shipped for GHSA-v6gv-fg46-h89j 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
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

All versions of `put` are vulnerable to Uninitialized Memory Exposure. The package incorrectly calculates the allocated Buffer size and does not trim the bytes written, which may allow attackers to access uninitialized memory containing sensitive data. This vulnerability only affects versions of Node.js <=6.x. ## Recommendation Upgrade your Node.js version or consider using an alternative package.

O3 Security · Impact-Aware SCA

Is GHSA-v6gv-fg46-h89j in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works