What is GHSA-GM9G-2G8V-FVXJ?

GHSA-GM9G-2G8V-FVXJ is a medium-severity uncontrolled resource consumption vulnerability in upmerge (npm), affecting versions <= 0.1.8. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-GM9G-2G8V-FVXJ?

GHSA-GM9G-2G8V-FVXJ has a CVSS score of 7.5 (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 upmerge are affected by GHSA-GM9G-2G8V-FVXJ?

upmerge (npm) versions <= 0.1.8 is affected.

Is there a fix for GHSA-GM9G-2G8V-FVXJ?

No fixed version is listed for GHSA-GM9G-2G8V-FVXJ yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-GM9G-2G8V-FVXJ exploitable, and should I be worried?

Whether GHSA-GM9G-2G8V-FVXJ 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-GM9G-2G8V-FVXJ 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-GM9G-2G8V-FVXJ?

No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

GHSA-GM9G-2G8V-FVXJ in upmerge

Q: How severe is GHSA-GM9G-2G8V-FVXJ?

GHSA-GM9G-2G8V-FVXJ has a CVSS score of 7.5 (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 upmerge are affected by GHSA-GM9G-2G8V-FVXJ?

upmerge (npm) versions <= 0.1.8 is affected.

Q: Is there a fix for GHSA-GM9G-2G8V-FVXJ?

No fixed version is listed for GHSA-GM9G-2G8V-FVXJ yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-GM9G-2G8V-FVXJ exploitable, and should I be worried?

Whether GHSA-GM9G-2G8V-FVXJ 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-GM9G-2G8V-FVXJ 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.

Q: How do I fix GHSA-GM9G-2G8V-FVXJ?

No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

Summary

Prototype Pollution in upmerge

All versions of upmerge are vulnerable to Prototype Pollution. The merge() function fails to prevent user input to alter an Object's prototype, allowing attackers to modify override properties of all objects in the application. This may lead to Denial of Service or may be chained with other vulnerabilities leading to Remote Code Execution.

Impact

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

GHSA-GM9G-2G8V-FVXJ has a CVSS score of 7.5 (Medium). The vector is network-reachable, 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. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

upmerge (<= 0.1.8)

Security releases

Not available

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

No fix is currently available. Consider using an alternative module until a fix is made available.

Frequently Asked Questions

What is GHSA-GM9G-2G8V-FVXJ? GHSA-GM9G-2G8V-FVXJ is a medium-severity uncontrolled resource consumption vulnerability in upmerge (npm), affecting versions <= 0.1.8. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-GM9G-2G8V-FVXJ? GHSA-GM9G-2G8V-FVXJ has a CVSS score of 7.5 (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 upmerge are affected by GHSA-GM9G-2G8V-FVXJ? upmerge (npm) versions <= 0.1.8 is affected.
Is there a fix for GHSA-GM9G-2G8V-FVXJ? No fixed version is listed for GHSA-GM9G-2G8V-FVXJ yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-GM9G-2G8V-FVXJ exploitable, and should I be worried? Whether GHSA-GM9G-2G8V-FVXJ 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-GM9G-2G8V-FVXJ 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-GM9G-2G8V-FVXJ? No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.