How severe is GHSA-4rgj-8mq3-hggj?

No CVSS score has been assigned to GHSA-4rgj-8mq3-hggj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4rgj-8mq3-hggj?

GHSA-4rgj-8mq3-hggj affects the following packages: @hapi/subtext (npm). Ecosystems affected: npm.

How do I fix GHSA-4rgj-8mq3-hggj?

Update @hapi/subtext to 6.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rgj-8mq3-hggj is resolved across your whole dependency graph.

How do I detect GHSA-4rgj-8mq3-hggj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/subtext. 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.

How do I mitigate GHSA-4rgj-8mq3-hggj 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-4rgj-8mq3-hggj?

O3 pinpoints whether GHSA-4rgj-8mq3-hggj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4rgj-8mq3-hggj actively exploited in the wild?

No public exploit code has been indexed for GHSA-4rgj-8mq3-hggj 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-4rgj-8mq3-hggj published, and has it been updated?

GHSA-4rgj-8mq3-hggj was published on September 3, 2020 and was last updated on August 31, 2020. 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-4rgj-8mq3-hggj

GHSA-4rgj-8mq3-hggj is a security vulnerability in @hapi/subtext. O3 Security confirms whether GHSA-4rgj-8mq3-hggj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in @hapi/subtext

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦@hapi/subtext

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Versions of @hapi/subtext prior to 6.1.2 are vulnerable to Denial of Service (DoS). The package fails to enforce the maxBytes configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.

Recommendation

Upgrade to version 6.1.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hapi/subtext`	all versions	6.1.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/subtext. 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.
Fix
Update @hapi/subtext to 6.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rgj-8mq3-hggj 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 pinpoints whether GHSA-4rgj-8mq3-hggj 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-4rgj-8mq3-hggj. 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/subtext` prior to 6.1.2 are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service. ## Recommendation Upgrade to version 6.1.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-4rgj-8mq3-hggj in your dependencies?

O3 detects GHSA-4rgj-8mq3-hggj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works