Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Prototype Pollution in pez

GHSA-g64q-3vg8-8f93

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 pez

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

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 pez are vulnerable to Prototype Pollution. A multipart payload can be constructed in a way that one of the parts’ content can be set as the entire payload object’s prototype. If this prototype contains data, it may bypass other validation rules which enforce access and privacy. If this prototype evaluates to null, it can cause unhandled exceptions when the request payload is accessed. Recommendation This package is deprecated and is now maintained as @hapi/pez. Please update your dependencies to use @hapi/pez.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-g64q-3vg8-8f93

  2. Revision 1 · created ·

    Published from osv record GHSA-g64q-3vg8-8f93

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-g64q-3vg8-8f93

Advisory: Prototype Pollution in pez
IDs: GHSA-g64q-3vg8-8f93
Record: https://patchnext.com/advisories/ghsa-g64q-3vg8-8f93 (revision 2, source checked 26 Oct 2026, 12:38 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 pez: affected every version

## Suggested inspection (read-only)
- `npm ls pez --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 pez.
- 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-g64q-3vg8-8f93 (OSV record GHSA-g64q-3vg8-8f93 lists affected ranges: npm pez >=0.0.0)
- Verified: https://github.com/advisories/GHSA-g64q-3vg8-8f93 (GitHub-reviewed advisory GHSA-g64q-3vg8-8f93 lists affected ranges: npm pez >=0.0.0)

Commands are suggestions: review each one before running it.

Loading voting…