How severe is GHSA-g9cg-h3jm-cwrc?

No CVSS score has been assigned to GHSA-g9cg-h3jm-cwrc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g9cg-h3jm-cwrc?

GHSA-g9cg-h3jm-cwrc affects the following packages: @hapi/pez (npm). Ecosystems affected: npm.

How do I fix GHSA-g9cg-h3jm-cwrc?

Update @hapi/pez to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9cg-h3jm-cwrc is resolved across your whole dependency graph.

How do I detect GHSA-g9cg-h3jm-cwrc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/pez, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g9cg-h3jm-cwrc if there is no patch (or I can't update yet)?

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.

Is GHSA-g9cg-h3jm-cwrc actively exploited in the wild?

No public exploit code has been indexed for GHSA-g9cg-h3jm-cwrc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g9cg-h3jm-cwrc published, and has it been updated?

GHSA-g9cg-h3jm-cwrc was published on September 3, 2020 and was last updated on September 26, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Prototype Pollution in @hapi/subtextGHSA-g9cg-h3jm-cwrc

GHSA-g9cg-h3jm-cwrc is a security vulnerability in @hapi/pez. A fix is available for @hapi/pez — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 26, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 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, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@hapi/peznpm

1.7Mdownloads / week

Description

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 request payload is accessed.

Recommendation

Upgrade to versions 5.0.1 or later. There is a fix available for version 4.1.2, but it only available for direct download from the repository.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hapi/pez`	all versions	5.0.1`npm install @hapi/pez@5.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/pez, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @hapi/pez to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9cg-h3jm-cwrc is resolved across your whole dependency graph.
Workarounds
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.

Frequently Asked Questions

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 request payload is accessed. ## Recommendation Upgrade to versions 5.0.1 or later. There is a fix available for version 4.1.2, but it only available for direct download from the repository.

O3 Security · Impact-Aware SCA

Is GHSA-g9cg-h3jm-cwrc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works