Unratedamended

Sensitive Data Exposure in put

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

npm put
Affected
every version
Fixed in
no fixed version recorded

Sources

Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-v6gv-fg46-h89j lists affected ranges: npm put >=0
VerifiedObserved 24 Oct 2026, 08:32 UTCStructured OSV record; GitHub-reviewed advisory.
GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-v6gv-fg46-h89j lists affected ranges: npm put >=0
VerifiedObserved 26 Oct 2026, 12:09 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation

Exploitation: No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS: not scored
EPSS: No dated EPSS signal available.

Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions

Published by the source: 3 Sep 2020, 16:48 UTC
Last modified by the source: 9 Jan 2023, 05:03 UTC
Source last checked: 26 Oct 2026, 12:09 UTC

Revision 2 · amended · 26 Oct 2026
Amended from ghsa record GHSA-v6gv-fg46-h89j
Revision 1 · created · 24 Oct 2026
Published from osv record GHSA-v6gv-fg46-h89j

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-v6gv-fg46-h89j

Advisory: Sensitive Data Exposure in put
IDs: GHSA-v6gv-fg46-h89j
Record: https://patchnext.com/advisories/ghsa-v6gv-fg46-h89j (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm put: affected every version

## Suggested inspection (read-only)
- `npm ls put --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on put.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v6gv-fg46-h89j (OSV record GHSA-v6gv-fg46-h89j lists affected ranges: npm put >=0)
- Verified: https://github.com/advisories/GHSA-v6gv-fg46-h89j (GitHub-reviewed advisory GHSA-v6gv-fg46-h89j lists affected ranges: npm put >=0)

Commands are suggestions: review each one before running it.

Loading voting…