npm package report

Is @hapi/pez safe?

1 known vulnerability, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
not scored

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-g9cg-h3jm-cwrc, the advisory selected below

// advisories

GHSA-g9cg-h3jm-cwrc

HIGH

Versions of @hapi/pez prior to 4.1.2 or 5.0.1 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

Affected
< 5.0.1
Fixed in
5.0.1
Weakness
CWE-1321
Published
2020-09-03
Source
github

GHSAreference

// dependencies

3 direct, 2 carrying known advisories, worst HIGH

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:50 UTC. The most recent advisory here was published 2020-09-03. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @hapi/pez safe? npm package security report | CyberXYZ