CVE-2026-121716
7.0HighPublished 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Local
- Complexity
- High
- Privileges
- None
- User action
- Required
- Impact
- Full C/I/A compromise
- Weakness
- CWE-78
What an attacker gets
Attackers can execute arbitrary commands as the current user if a victim runs a poisoned fzf-tmux command. This requires the victim to execute a crafted fzf-tmux command provided by a malicious plugin or project configuration.
Root cause
The bin/fzf-tmux script fails to validate layout and geometry arguments before passing them to Bash arithmetic expansion and tmux commands.
Affected versions
fzf versions prior to 0.74.5
CVSS v3.1 · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade fzf to version 0.74.5 or later. If you cannot upgrade, audit and restrict the use of fzf-tmux wrappers or plugins that accept untrusted input for layout or geometry flags.
$ fzf --versionAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
fzf is a command-line fuzzy finder. Prior to 0.74.5, bin/fzf-tmux validates separately supplied layout sizes but does not validate attached -l and -u layout values before Bash arithmetic expansion, allowing command substitution in a crafted operand to execute as the invoking user during option parsing. The same validation failure lets space-bearing popup geometry options -x, -y, -w, -h, and -p reach an unquoted tmux popup option string and inject additional tmux flags. Exploitation requires less-trusted project configuration, a wrapper, or a plugin to supply the poisoned value and requires the victim to invoke fzf-tmux; normal values are usually trusted, and the script has been superseded by built-in tmux options. This issue is fixed in version 0.74.5.