EUVD-2026-35297
GHSA-4cw9-jpqf-99x8
Severity by source
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A security vulnerability has been detected in tmux up to 3.6a. Affected is the function image_free of the file image.c. Such manipulation leads to use after free. Local access is required to approach this attack. This attack is characterized by high complexity. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. Upgrading to version 3.7-rc is able to address this issue. The name of the patch is fc6d94a9f8a593bd8b7031650802084385d4ee03. The affected component should be upgraded.
AnalysisAI
Use-after-free memory corruption in tmux's SIXEL image handling allows a local low-privileged attacker with high complexity to trigger memory corruption or denial of service in versions up to 3.6a. The root cause lies in the image_free() function in image.c, where image structs retain stale pointers to their original parent screen's image list after alternate screen transitions, causing TAILQ_REMOVE to dereference an invalid list pointer. No active exploitation is confirmed (not in CISA KEV), though publicly available exploit code exists per the CVE vector's E:P designation and a public gist from XlabAITeam. A fix is available in tmux 3.7-rc.
Technical ContextAI
tmux supports SIXEL, a graphics protocol for rendering pixel images in terminal sessions, compiled in via the ENABLE_SIXEL preprocessor flag. The vulnerable image_free() function in image.c originally derived the image list to remove from using im->s - a pointer back to the owning screen struct. However, tmux manages two image queues per screen: s->images (primary screen) and s->saved_images (alternate screen). When screen_alternate_on() or screen_alternate_off() transitions images between these queues, the im->s reference becomes stale or incorrect relative to the list the image now belongs to. Calling TAILQ_REMOVE(&s->images, im, entry) on an image that was moved to s->saved_images constitutes a CWE-416 use-after-free, corrupting the linked-list structure. The fix introduces a direct im->list pointer on the image struct, set at insertion time via image_store() and updated correctly during screen transitions in screen_alternate_on() and screen_alternate_off(). The bug only exists in SIXEL-enabled tmux builds.
RemediationAI
The primary fix is to upgrade tmux to version 3.7-rc or later, which contains patch commit fc6d94a9f8a593bd8b7031650802084385d4ee03, available at https://github.com/tmux/tmux/commit/fc6d94a9f8a593bd8b7031650802084385d4ee03 and as a tagged release at https://github.com/tmux/tmux/releases/tag/3.7-rc. Note that 3.7-rc is a release candidate; administrators should monitor for a stable 3.7 release for production deployments. If immediate upgrading is not possible and SIXEL image rendering is not required, recompiling tmux from source without the ENABLE_SIXEL compile-time flag eliminates the entire vulnerable code path - the affected image_free logic is inside #ifdef ENABLE_SIXEL guards. The trade-off is loss of in-terminal SIXEL image rendering capability. Many standard distribution packages (e.g., Debian, Ubuntu) ship tmux without SIXEL enabled by default, so verifying your build's compile flags via tmux -V or package metadata is a quick first triage step.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today