How severe is GHSA-5854-jvxx-2cg9?

No CVSS score has been assigned to GHSA-5854-jvxx-2cg9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5854-jvxx-2cg9?

GHSA-5854-jvxx-2cg9 affects the following packages: content (npm). Ecosystems affected: npm.

How do I fix GHSA-5854-jvxx-2cg9?

No patched version of content has shipped for GHSA-5854-jvxx-2cg9 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-5854-jvxx-2cg9 in my npm dependencies?

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

How do I mitigate GHSA-5854-jvxx-2cg9 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-5854-jvxx-2cg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5854-jvxx-2cg9 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-5854-jvxx-2cg9 published, and has it been updated?

GHSA-5854-jvxx-2cg9 was published on September 3, 2020 and was last updated on September 29, 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

Denial of Service in contentGHSA-5854-jvxx-2cg9

GHSA-5854-jvxx-2cg9 is a security vulnerability in content. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Sep 29, 2025

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

contentnpm

64Kdownloads / week

Description

Versions of content 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

This package is deprecated and is now maintained as @hapi/content. Please update your dependencies to use @hapi/content.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`content`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for content, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of content has shipped for GHSA-5854-jvxx-2cg9 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Versions of `content` 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 This package is deprecated and is now maintained as `@hapi/content`. Please update your dependencies to use

O3 Security · Impact-Aware SCA

Is GHSA-5854-jvxx-2cg9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works