# CVE-2026-48111: GHSL-2026-121 7-Zip UEFI DEPEX OOB Read

> An off-by-one error in 7-Zip's UEFI parser allows attackers to trigger a crash or leak minor string data via crafted archives.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** ALPINE-CVE-2026-48111, DEBIAN-CVE-2026-48111, ECHO-358c-a231-063b, MINI-45xm-5x8x-pqrp, UBUNTU-CVE-2026-48111

## What is CVE-2026-48111?

CVE-2026-48111 is a medium-severity vulnerability in mcmilk 7-Zip, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

7-Zip is a file archiver with a high compression ratio. Versions 9.21 through 26.00 contain an off-by-one out-of-bounds read vulnerability in the ParseDepedencyExpression function of the UEFI firmware image parser(CPP/7zip/Archive/UefiHandler.cpp). The function validates an attacker-controlled opcode byte using > instead of >= against the element count of the 10-entry kExpressionCommands static array, allowing an opcode value of 10 to read one pointer slot (8 bytes on x64) past the end of the array in .rodata. The out-of-bounds value is then dereferenced as a const char * and passed through strlen and memcpy into the archive's Characts property, which may cause either a denial of service (access violation when the adjacent bytes do not form a valid readable pointer) or a minor information disclosure of an adjacent .rdata string literal into archive metadata. The vulnerability is reached automatically during IInArchive::Open() via the call path OpenFv/OpenCapsule → ParseVolume → ParseSections when processing a SECTION_DXE_DEPEX (0x13) or SECTION_PEI_DEPEX (0x1B) section whose first body byte is 0x0A, and the UEFI handler is enabled by default in stock 7z.dll with signature-based detection for both UEFIc and UEFIf formats. The outcome (crash vs. silent leak) is deterministic per build but linker-layout dependent, with no write primitive and no disclosure of heap data, secrets, or ASLR base addresses. Version 26.01 fixes the issue.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-48111?

It affects 1 product.


Products: 7-Zip 7-Zip.

## How do I fix CVE-2026-48111?

Upgrade to a fixed version.

## Is CVE-2026-48111 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48111 exists.

## Other vulnerabilities in mcmilk 7-Zip

- [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-2026-48111 and fix it if it is affected.

What it is: CVE-2026-48111 is a medium-severity vulnerability in mcmilk 7-Zip, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48111 exists.

Affected product: mcmilk 7-Zip. 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-2026-48111/ (Markdown: https://insights.sbomify.com/CVE-2026-48111/index.md)
```

## Sources

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

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