What is GHSA-4XCV-9JJX-GFJ3?

GHSA-4XCV-9JJX-GFJ3 is a medium-severity uncontrolled resource consumption vulnerability in mem (npm), affecting versions < 4.0.0. It is fixed in 4.0.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-4XCV-9JJX-GFJ3?

GHSA-4XCV-9JJX-GFJ3 has a CVSS score of 5.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of mem are affected by GHSA-4XCV-9JJX-GFJ3?

mem (npm) versions < 4.0.0 is affected.

Is there a fix for GHSA-4XCV-9JJX-GFJ3?

Yes. GHSA-4XCV-9JJX-GFJ3 is fixed in 4.0.0. Upgrade to this version or later.

Is GHSA-4XCV-9JJX-GFJ3 exploitable, and should I be worried?

Whether GHSA-4XCV-9JJX-GFJ3 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.

What actually determines whether GHSA-4XCV-9JJX-GFJ3 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.

GHSA-4XCV-9JJX-GFJ3 in mem

Q: How severe is GHSA-4XCV-9JJX-GFJ3?

GHSA-4XCV-9JJX-GFJ3 has a CVSS score of 5.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of mem are affected by GHSA-4XCV-9JJX-GFJ3?

mem (npm) versions < 4.0.0 is affected.

Q: Is there a fix for GHSA-4XCV-9JJX-GFJ3?

Yes. GHSA-4XCV-9JJX-GFJ3 is fixed in 4.0.0. Upgrade to this version or later.

Q: Is GHSA-4XCV-9JJX-GFJ3 exploitable, and should I be worried?

Whether GHSA-4XCV-9JJX-GFJ3 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.

Q: What actually determines whether GHSA-4XCV-9JJX-GFJ3 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.

Summary

Denial of Service in mem

Versions of mem prior to 4.0.0 are vulnerable to Denial of Service (DoS). The package fails to remove old values from the cache even after a value passes its maxAge property. This may allow attackers to exhaust the system's memory if they are able to abuse the application logging.

Impact

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

GHSA-4XCV-9JJX-GFJ3 has a CVSS score of 5.1 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.0.0); upgrading removes the vulnerable code path.

Affected versions

mem (< 4.0.0)

Security releases

mem → 4.0.0 (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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade to version 4.0.0 or later.

Frequently Asked Questions

What is GHSA-4XCV-9JJX-GFJ3? GHSA-4XCV-9JJX-GFJ3 is a medium-severity uncontrolled resource consumption vulnerability in mem (npm), affecting versions < 4.0.0. It is fixed in 4.0.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-4XCV-9JJX-GFJ3? GHSA-4XCV-9JJX-GFJ3 has a CVSS score of 5.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of mem are affected by GHSA-4XCV-9JJX-GFJ3? mem (npm) versions < 4.0.0 is affected.
Is there a fix for GHSA-4XCV-9JJX-GFJ3? Yes. GHSA-4XCV-9JJX-GFJ3 is fixed in 4.0.0. Upgrade to this version or later.
Is GHSA-4XCV-9JJX-GFJ3 exploitable, and should I be worried? Whether GHSA-4XCV-9JJX-GFJ3 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
What actually determines whether GHSA-4XCV-9JJX-GFJ3 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.
How do I fix GHSA-4XCV-9JJX-GFJ3? Upgrade mem to 4.0.0 or later.