Sandbox escape via executable MIME handler
Published May 24, 2026 · Updated May 24, 2026
Sandbox escape in Wine 0.9 through 11.0 allows local users to run Windows executables outside Flatpak or Snap confinement via desktop MIME handling. The loader/wine.desktop entry registers executable MIME types and sends a selected file to wine start /unix, which loads it as code rather than data. Exploitation requires an unsandboxed Wine handler, and automatic execution requires Wine to be the only handler; resulting code receives the invoker's host permissions.
Summary
What happened
Sandbox escape in Wine 0.9 through 11.0 allows local users to run Windows executables outside Flatpak or Snap confinement via desktop MIME handling. The loader/wine.desktop entry registers executable MIME types and sends a selected file to wine start /unix, which loads it as code rather than data. Exploitation requires an unsandboxed Wine handler, and automatic execution requires Wine to be the only handler; resulting code receives the invoker's host permissions.
The record
- CVE
- CVE-2026-48831
- Published
- May 24, 2026
- Updated
- May 24, 2026
- Vendor
- WineHQ
- Product
- Wine
- Classifications
- CWE-669, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2026CVE publishedPublication date reported by the CVE source.
- May 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.9 <=11.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo