CVE-2026-123014 · Other
NO FIX YET · SEE WHAT TO DO
iTerm2 before 3.7.7beta2 mishandles the x-man-page: URL handler, so percent-encoded NUL characters survive sanitization and become whitespace, letting an attacker inject extra arguments into /usr/bin/man. Injecting the -P option selects an attacker-controlled pager command, which runs with the privileges of the logged-in user once the victim opens the crafted URL.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Anyone running iTerm2 before 3.7.7beta2 on macOS is exposed when they open a crafted x-man-page: link in the terminal. The sources do not describe a server-side path, so teams with no iTerm2 installs on developer machines can skip it.
Not affected if iterm2-3.7.7beta2-or-later, no-iterm2-installed
Who cares developer-workstations, iterm2, macos
defaults read com.googlecode.iterm2 Version (exact key unknown from sources)3.7.7beta23.7.7beta2 (fixed version stated by the product range; earlier versions affected)iTerm2 before 3.7.7beta2 has an argument injection vulnerability in the x-man-page: URL handler, allowing an attacker to execute arbitrary commands with the privileges of the logged-in user by inducing the user to open a crafted URL in iTerm2. Percent-encoded NUL characters survive input sanitization and are subsequently converted to whitespace during command-line parsing, allowing injection of additional arguments to /usr/bin/man. An attacker can inject the -P option to select an attacker-controlled pager command. NOTE: this issue exists because of an incomplete fix for CVE-2023-46321.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.