# CVE-2026-48831: Security feature bypass in Wine

> Wine's MIME handler configuration allows blind execution of EXE files, enabling attackers to escape Flatpak and Snap sandboxes.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/AU:N/V:D/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2026
- **Updated:** 27 May 2026
- **Also known as:** DEBIAN-CVE-2026-48831, GHSA-h8w5-58rh-75vr, UBUNTU-CVE-2026-48831

## What is CVE-2026-48831?

CVE-2026-48831 is a high-severity vulnerability in WineHQ Wine, published on 24 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Wine ships a .desktop file that registers itself as a MIME handler for EXE files and several other Windows executable file types. In some configurations, handling of an EXE file causes that file to be blindly executed with the permissions of the invoker. This allows escaping Flatpak and Snap sandboxes, because MIME handlers are not intended for use by code interpreters and loaders. NOTE: some parties feel that this is not a bug to be addressed in Wine, because there is no known solution that avoids a severe loss of usability (Wine could be a binfmt-misc handler, but binfmt-misc does not exist on all platforms supported by Wine).

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

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

## Is CVE-2026-48831 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48831 and fix it if it is affected.

What it is: CVE-2026-48831 is a high-severity vulnerability in WineHQ Wine, published on 24 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-48831 in the wild and no public exploit code.

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

## Sources

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

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