# CVE-2025-27614: Gitk allows arbitrary command execution

> Attackers can execute arbitrary scripts via crafted Git repositories when users open files in Gitk, requiring user interaction.

- **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2025-27614, AZL-65079, BELL-CVE-2025-27614, DEBIAN-CVE-2025-27614, ECHO-4efe-e848-a641, GHSA-g4v5-fjv9-mhhc, UBUNTU-CVE-2025-27614

## What is CVE-2025-27614?

CVE-2025-27614 is a high-severity command injection vulnerability in j6t gitk, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Gitk is a Tcl/Tk based Git history browser. Starting with 2.41.0, a Git repository can be crafted in such a way that with some social engineering a user who has cloned the repository can be tricked into running any script (e.g., Bourne shell, Perl, Python, ...) supplied by the attacker by invoking gitk filename, where filename has a particular structure. The script is run with the privileges of the user. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-27614?


## How do I fix CVE-2025-27614?

Upgrade to a fixed version.

## Is CVE-2025-27614 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27614 and fix it if it is affected.

What it is: CVE-2025-27614 is a high-severity command injection vulnerability in j6t gitk, published on 10 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-27614 in the wild and no public exploit code.

Affected product: j6t gitk. 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-2025-27614/ (Markdown: https://insights.sbomify.com/CVE-2025-27614/index.md)
```

## Sources

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

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