# CVE-2022-37614: mockery is vulnerable to prototype pollution

> Prototype pollution in mockery.js allows attackers to modify object prototypes, potentially leading to code execution or security bypasses in Node.js applications.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** GHSA-gmwp-3pwc-3j3g

## What is CVE-2022-37614?

CVE-2022-37614 is a critical vulnerability in n/a, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prototype pollution vulnerability in function enable in mockery.js in mfncooper mockery commit 822f0566fd6d72af8c943ae5ca2aa92e516aa2cf via the key variable in mockery.js.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2022-37614?

2 open source packages ship an affected version, including mockery. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mockery` | npm | All versions to 2.1.0 | None |
| `mockery` | npm | All versions to 2.1.0 | None |

Products: Mockery Project Mockery.

## How do I fix CVE-2022-37614?

No fix has been published for CVE-2022-37614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-37614 being exploited?

There is no known exploitation of CVE-2022-37614 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37614 and fix it if it is affected.

What it is: CVE-2022-37614 is a critical vulnerability in n/a, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-37614 in the wild and no public exploit code.

Affected packages and fixed versions:
- mockery (npm): affected all versions up to 2.1.0; no fix listed
- mockery (npm): affected all versions up to 2.1.0; 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/CVE-2022-37614/ (Markdown: https://insights.sbomify.com/CVE-2022-37614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-37614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-37614
- OSV: https://osv.dev/vulnerability/CVE-2022-37614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-37614/
Summaries are generated and may contain mistakes; the official description above is the record.