# GHSA-3f95-w5h5-fq86: Prototype Pollution in mergify


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Sep 2020

## What is GHSA-3f95-w5h5-fq86?

GHSA-3f95-w5h5-fq86 is a vulnerability in mergify, published on 11 Sep 2020. 

### Official description

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.

## Recommendation

No fix is currently available. Consider using an alternative module as the package is deprecated.

## Which versions are affected by GHSA-3f95-w5h5-fq86?

2 open source packages ship an affected version, including mergify.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mergify` | npm | All versions | None |
| `mergify` | npm | All versions | None |

## How do I fix GHSA-3f95-w5h5-fq86?

No fix has been published for GHSA-3f95-w5h5-fq86 yet. Limit exposure of the affected software until one is available.

## Is GHSA-3f95-w5h5-fq86 being exploited?

There is no known exploitation of GHSA-3f95-w5h5-fq86 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3f95-w5h5-fq86 and fix it if it is affected.

What it is: GHSA-3f95-w5h5-fq86 is a vulnerability in mergify, published on 11 Sep 2020. 
Exploitation: There is no known exploitation of GHSA-3f95-w5h5-fq86 in the wild and no public exploit code.

Affected packages and fixed versions:
- mergify (npm): affected all versions; no fix listed
- mergify (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-3f95-w5h5-fq86/ (Markdown: https://insights.sbomify.com/GHSA-3f95-w5h5-fq86/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3f95-w5h5-fq86

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3f95-w5h5-fq86/
Summaries are generated and may contain mistakes; the official description above is the record.