How severe is GHSA-pv6r-vchh-cxg9?

No CVSS score has been assigned to GHSA-pv6r-vchh-cxg9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pv6r-vchh-cxg9?

GHSA-pv6r-vchh-cxg9 affects the following packages: apostrophe (npm). Ecosystems affected: npm.

How do I fix GHSA-pv6r-vchh-cxg9?

Update apostrophe to 2.97.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pv6r-vchh-cxg9 is resolved across your whole dependency graph.

How do I detect GHSA-pv6r-vchh-cxg9 in my npm dependencies?

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

How do I mitigate GHSA-pv6r-vchh-cxg9 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-pv6r-vchh-cxg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pv6r-vchh-cxg9 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-pv6r-vchh-cxg9 published, and has it been updated?

GHSA-pv6r-vchh-cxg9 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 apostropheGHSA-pv6r-vchh-cxg9

GHSA-pv6r-vchh-cxg9 is a security vulnerability in apostrophe. A fix is available for apostrophe — 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.

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

apostrophenpm

11Kdownloads / week

Description

Versions of apostrophe prior to 2.97.1 are vulnerable to Denial of Service. The apostrophe-jobs module sets a callback for incoming jobs and doesn't clear it regardless of its status. This causes the server to accumulate callbacks, allowing an attacker to start a large number of jobs and exhaust system memory.

Recommendation

Upgrade to version 2.97.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`apostrophe`	all versions	2.97.1`npm install apostrophe@2.97.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apostrophe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update apostrophe to 2.97.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pv6r-vchh-cxg9 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

Versions of `apostrophe` prior to 2.97.1 are vulnerable to Denial of Service. The `apostrophe-jobs` module sets a callback for incoming jobs and doesn't clear it regardless of its status. This causes the server to accumulate callbacks, allowing an attacker to start a large number of jobs and exhaust system memory. ## Recommendation Upgrade to version 2.97.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-pv6r-vchh-cxg9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works