Local server crash via wrong-list image unlink
Published Jun 9, 2026 · Updated Jun 9, 2026
Use-after-free in tmux 3.6a allows local users to crash the server by removing SIXEL images while an alternate screen is active. image_free unconditionally unlinks an image from the active image list after alternate-screen handling has moved that image to the saved list, corrupting list state before freeing it. Exploitation requires a local session, a build compiled with --enable-sixel, and crafted terminal input; upstream has demonstrated only a server crash.
Summary
What happened
Use-after-free in tmux 3.6a allows local users to crash the server by removing SIXEL images while an alternate screen is active. image_free unconditionally unlinks an image from the active image list after alternate-screen handling has moved that image to the saved list, corrupting list state before freeing it. Exploitation requires a local session, a build compiled with --enable-sixel, and crafted terminal input; upstream has demonstrated only a server crash.
The record
- CVE
- CVE-2026-11623
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- tmux
- Product
- tmux
- Classifications
- CWE-119, CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 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=3.6a
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
- XlabAITeam tmux SIXEL crash proof of conceptproof of concept · demonstrated
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