How severe is GHSA-cvfm-xjc8-f2vm?

No CVSS score has been assigned to GHSA-cvfm-xjc8-f2vm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cvfm-xjc8-f2vm?

GHSA-cvfm-xjc8-f2vm affects the following packages: @commercial/subtext (npm). Ecosystems affected: npm.

How do I fix GHSA-cvfm-xjc8-f2vm?

Update @commercial/subtext to 5.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvfm-xjc8-f2vm is resolved across your whole dependency graph.

How do I detect GHSA-cvfm-xjc8-f2vm in my npm dependencies?

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

How do I mitigate GHSA-cvfm-xjc8-f2vm 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-cvfm-xjc8-f2vm actively exploited in the wild?

No public exploit code has been indexed for GHSA-cvfm-xjc8-f2vm 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-cvfm-xjc8-f2vm published, and has it been updated?

GHSA-cvfm-xjc8-f2vm 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

Denial of Service in @commercial/subtextGHSA-cvfm-xjc8-f2vm

GHSA-cvfm-xjc8-f2vm is a security vulnerability in @commercial/subtext. A fix is available for @commercial/subtext — see the affected versions and patch details below.

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

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.

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

@commercial/subtextnpm

29downloads / week

Description

Version 5.1.1 of @commercial/subtext is 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.1.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@commercial/subtext`	≥ 5.1.1&&< 5.1.2	5.1.2`npm install @commercial/subtext@5.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 @commercial/subtext, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @commercial/subtext to 5.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvfm-xjc8-f2vm is resolved across your whole dependency graph.
Workarounds
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

Version 5.1.1 of `@commercial/subtext` is 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.1.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-cvfm-xjc8-f2vm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works