CVE-2025-27614 | Gitk allows arbitrary command execution

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.

Published: 2025-07-10 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-27614 is rated Low Risk (35.7/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-27614

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-07-11 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-27614

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.6 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 6.0 [email protected]

Weakness enumeration for CVE-2025-27614

OS Trackers for CVE-2025-27614

vendor priority summary link
alpine high CVE-2025-27614: 1 source package rows (git); 5 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2025-27614
debian unimportant CVE-2025-27614 unimportant priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-27614
gentoo high CVE-2025-27614: 1 GLSA(s) (202507-09), 1 atom(s) (dev-vcs/git); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-27614
redhat medium — https://access.redhat.com/security/cve/CVE-2025-27614
suse high CVE-2025-27614 severity important: SUSE including 126 source package names (0.0.17-1.1:git-core-2.51.0-150600.3.12.1, 0.1.6-1.2:git-2.51.0-150600.3.12.1, …), 363 product×package rows across 51 product lines (Container bci/kiwi, Container bci/spack, … (51 product lines)): Fixed 293, Known Not Affected 70. https://www.suse.com/security/cve/CVE-2025-27614/
ubuntu medium CVE-2025-27614 medium priority: Ubuntu including 1 source packages (git), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, upstream, xenial): not-affected 4, released 4. https://ubuntu.com/security/CVE-2025-27614

Affected software / configurations for CVE-2025-27614

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-27614

cvelogic Threat Intelligence