Which versions of mergify are affected by GHSA-3F95-W5H5-FQ86?

mergify (npm) versions >= 0 is affected.

Is there a fix for GHSA-3F95-W5H5-FQ86?

No fixed version is listed for GHSA-3F95-W5H5-FQ86 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-3F95-W5H5-FQ86 exploitable, and should I be worried?

Whether GHSA-3F95-W5H5-FQ86 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-3F95-W5H5-FQ86 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-3F95-W5H5-FQ86 in mergify

GHSA-3F95-W5H5-FQ86

GHSA-3F95-W5H5-FQ86 is a medium-severity security vulnerability in mergify (npm), affecting versions >= 0. No fixed version is listed yet.

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

Prototype Pollution in mergify

All versions of mergify are vulnerable to Prototype Pollution. The mergify() function allows attackers to modify the prototype of Object causing the addition or modification of an existing property that will exist on all objects.

Impact

Affected versions

mergify (>= 0)

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 as the package is deprecated.

Frequently Asked Questions

What is GHSA-3F95-W5H5-FQ86? GHSA-3F95-W5H5-FQ86 is a medium-severity security vulnerability in mergify (npm), affecting versions >= 0. No fixed version is listed yet.
Which versions of mergify are affected by GHSA-3F95-W5H5-FQ86? mergify (npm) versions >= 0 is affected.
Is there a fix for GHSA-3F95-W5H5-FQ86? No fixed version is listed for GHSA-3F95-W5H5-FQ86 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-3F95-W5H5-FQ86 exploitable, and should I be worried? Whether GHSA-3F95-W5H5-FQ86 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-3F95-W5H5-FQ86 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.