How severe is GHSA-3wqh-h42r-x8fq?

No CVSS score has been assigned to GHSA-3wqh-h42r-x8fq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3wqh-h42r-x8fq?

GHSA-3wqh-h42r-x8fq affects the following packages: @hapi/content (npm). Ecosystems affected: npm.

How do I fix GHSA-3wqh-h42r-x8fq?

Update @hapi/content to 5.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wqh-h42r-x8fq is resolved across your whole dependency graph.

How do I detect GHSA-3wqh-h42r-x8fq in my npm dependencies?

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

How do I mitigate GHSA-3wqh-h42r-x8fq 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.

How does O3 Security protect against GHSA-3wqh-h42r-x8fq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3wqh-h42r-x8fq can be triaged on real exposure rather than presence alone.

Is GHSA-3wqh-h42r-x8fq actively exploited in the wild?

No public exploit code has been indexed for GHSA-3wqh-h42r-x8fq 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-3wqh-h42r-x8fq published, and has it been updated?

GHSA-3wqh-h42r-x8fq was published on September 3, 2020 and was last updated on September 25, 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

GHSA-3wqh-h42r-x8fq — @hapi/content

GHSA-3wqh-h42r-x8fq is a security vulnerability in @hapi/content. A fix is available for @hapi/content — see the affected versions and patch details below.

Denial of Service in @hapi/content

Published

Sep 3, 2020

Updated

Sep 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 25, 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.

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

@hapi/contentnpm

995Kdownloads / week

Description

Versions of @hapi/content prior to 4.1.1 and 5.0.1 are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.

Recommendation

Upgrade to version 5.0.2. Versions 4.1.1 and 5.0.1 are fixed but only available for direct download through the repository.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hapi/content`	all versions	5.0.2`npm install @hapi/content@5.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/content, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @hapi/content to 5.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wqh-h42r-x8fq 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3wqh-h42r-x8fq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3wqh-h42r-x8fq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `@hapi/content` prior to 4.1.1 and 5.0.1 are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services. ## Recommendation Upgrade to version 5.0.2. Versions 4.1.1 and 5.0.1 are fixed but only avail

O3 Security · Impact-Aware SCA

Is GHSA-3wqh-h42r-x8fq in your dependencies?

O3 Security finds GHSA-3wqh-h42r-x8fq across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works