# CVE-2022-29072: Memory corruption in n/a

> Heap overflow in 7-Zip allows command execution when a malicious .7z file is dragged to the Help contents area.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2022
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-37mw-x654-r2j8

## What is CVE-2022-29072?

CVE-2022-29072 is a high-severity memory corruption vulnerability in n/a, published on 15 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

7-Zip through 21.07 on Windows allows privilege escalation and command execution when a file with the .7z extension is dragged to the Help>Contents area. This is caused by misconfiguration of 7z.dll and a heap overflow. The command runs in a child process under the 7zFM.exe process. NOTE: multiple third parties have reported that no privilege escalation can occur

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: 7-Zip 7-Zip.

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

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

## Is CVE-2022-29072 being exploited?

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

Public exploit code:

- 7-Zip through 21.07 on Windows allows privilege escalation and command execution when a file with the .7z extension is dragged to the Help>Contents area. (github_poc): https://github.com/kagancapar/CVE-2022-29072
- ** DISPUTED ** 7-Zip through 21.07 on Windows allows privilege escalation and command execution when a file with the .7z extension is dragged to the Help>Contents area. This is caused by misconfiguration of 7z.dll and a heap overflow. The command runs in a child process under the 7zFM.exe process, NOTE: multiple third parties have reported that no privilege escalation can occur. (github_poc): https://github.com/sentinelblue/CVE-2022-29072
- Powershell to mitigate CVE-2022-29072 (github_poc): https://github.com/tiktb8/CVE-2022-29072
- 7-Zip CVE-2022-29072 Mitigation - CHM file - This script detects if the .chm file exists and removes it. (github_poc): https://github.com/Phantomiman/7-Zip.chm-Mitigation
- https://github.com/rasan2001/CVE-2022-29072 (github_poc): https://github.com/rasan2001/CVE-2022-29072

## Other vulnerabilities in n/a

- [CVE-2025-0411](https://insights.sbomify.com/CVE-2025-0411/): 7-Zip Mark of the Web Bypass (high 7.0, exploited in the wild)
- [CVE-2008-6536](https://insights.sbomify.com/CVE-2008-6536/): Other in n/a (critical 10.0)
- [CVE-2026-48095](https://insights.sbomify.com/CVE-2026-48095/): GHSL-2026-140_7-Zip: 7-Zip has a heap buffer overflow via NTFS compressed stream buffer under-allocation (high 8.8)
- [CVE-2018-10172](https://insights.sbomify.com/CVE-2018-10172/): Privilege escalation in n/a (high 8.8)
- [CVE-2016-2335](https://insights.sbomify.com/CVE-2016-2335/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29072 is a high-severity memory corruption vulnerability in n/a, published on 15 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29072 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-29072/ (Markdown: https://insights.sbomify.com/CVE-2022-29072/index.md)
```

## Sources

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

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