Unratedamended

Prototype Pollution in sahmat

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 sahmat
Affected
every version
Fixed in
no fixed version recorded

Sources

GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-83pq-466j-fc6j lists affected ranges: npm sahmat >=0.0.0
VerifiedObserved 26 Oct 2026, 12:08 UTCStructured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-83pq-466j-fc6j lists affected ranges: npm sahmat >=0.0.0
VerifiedObserved 24 Oct 2026, 08:32 UTCStructured OSV record; GitHub-reviewed advisory.

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 sahmat are vulnerable to prototype pollution. The package does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects. Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

Dates and revisions

Published by the source: 4 Sep 2020, 15:17 UTC
Last modified by the source: 9 Jan 2023, 05:03 UTC
Source last checked: 26 Oct 2026, 12:08 UTC

Revision 2 · amended · 26 Oct 2026
Amended from ghsa record GHSA-83pq-466j-fc6j
Revision 1 · created · 24 Oct 2026
Published from osv record GHSA-83pq-466j-fc6j

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-83pq-466j-fc6j

Advisory: Prototype Pollution in sahmat
IDs: GHSA-83pq-466j-fc6j
Record: https://patchnext.com/advisories/ghsa-83pq-466j-fc6j (revision 2, source checked 26 Oct 2026, 12:08 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 sahmat: affected every version

## Suggested inspection (read-only)
- `npm ls sahmat --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 sahmat.
- 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://github.com/advisories/GHSA-83pq-466j-fc6j (GitHub-reviewed advisory GHSA-83pq-466j-fc6j lists affected ranges: npm sahmat >=0.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-83pq-466j-fc6j (OSV record GHSA-83pq-466j-fc6j lists affected ranges: npm sahmat >=0.0.0)

Commands are suggestions: review each one before running it.

Loading voting…