Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-g64q-3vg8-8f93

GHSA-g64q-3vg8-8f93 is a security vulnerability in pez. O3 Security confirms whether GHSA-g64q-3vg8-8f93 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in pez

Published
Sep 3, 2020
Updated
Sep 30, 2025
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Sep 30, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

peznpm
92Kdownloads / week

Description

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmpez0.0.0No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pez. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of pez has shipped for GHSA-g64q-3vg8-8f93 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-g64q-3vg8-8f93 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g64q-3vg8-8f93. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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`.
O3 Security · Impact-Aware SCA

Is GHSA-g64q-3vg8-8f93 in your dependencies?

O3 detects GHSA-g64q-3vg8-8f93 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-g64q-3vg8-8f93: Prototype Pollution in… | O3 Security