# CVE-2026-123014: iTerm2 before 3.7.7beta2 has an argument injection vulnerability in the x-man-page: URL handler, allowing an attacker to execute arbitrary c


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-9hxf-w2gf-j4wv

## What is CVE-2026-123014?

CVE-2026-123014 is a high-severity vulnerability in iTerm2, published on 5 Nov 2026. 

### Official description

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.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-123014?


## How do I fix CVE-2026-123014?

No fix has been published for CVE-2026-123014 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123014 being exploited?

There is no known exploitation of CVE-2026-123014 in the wild and no public exploit code.

Public exploit code:

- PoC and research for CVE-2026-123014: iTerm2 x-man-page NUL-byte argument injection. (github_poc): https://github.com/giki-shergill/CVE-2026-123014---iTerm2-Terminal

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123014 and fix it if it is affected.

What it is: CVE-2026-123014 is a high-severity vulnerability in iTerm2, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123014 in the wild and no public exploit code.

Affected product: iTerm2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123014/ (Markdown: https://insights.sbomify.com/CVE-2026-123014/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123014
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123014
- OSV: https://osv.dev/vulnerability/CVE-2026-123014

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123014/
Summaries are generated and may contain mistakes; the official description above is the record.