GHSA-PV6R-VCHH-CXG9

GHSA-PV6R-VCHH-CXG9 is a low-severity uncontrolled resource consumption vulnerability in apostrophe (npm), affecting versions < 2.97.1. It is fixed in 2.97.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Denial of Service in apostrophe

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.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

apostrophe (< 2.97.1)

Security releases

apostrophe → 2.97.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade to version 2.97.1 or later.

Frequently Asked Questions

  1. What is GHSA-PV6R-VCHH-CXG9? GHSA-PV6R-VCHH-CXG9 is a low-severity uncontrolled resource consumption vulnerability in apostrophe (npm), affecting versions < 2.97.1. It is fixed in 2.97.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
  2. Which versions of apostrophe are affected by GHSA-PV6R-VCHH-CXG9? apostrophe (npm) versions < 2.97.1 is affected.
  3. Is there a fix for GHSA-PV6R-VCHH-CXG9? Yes. GHSA-PV6R-VCHH-CXG9 is fixed in 2.97.1. Upgrade to this version or later.
  4. Is GHSA-PV6R-VCHH-CXG9 exploitable, and should I be worried? Whether GHSA-PV6R-VCHH-CXG9 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-PV6R-VCHH-CXG9 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-PV6R-VCHH-CXG9? Upgrade apostrophe to 2.97.1 or later.

Other vulnerabilities in apostrophe

Stop the waste.
Protect your environment with Kodem.