CVE-2025-27613 | Gitk can create and truncate files in the user's home directory

Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). 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.1.

Published: 2025-07-10 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-27613 is rated Low Risk (21.7/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.29%). Mandatory action: 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-27613

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 2026-06-15 0.02% 0.29% +0.27%
2 2025-07-11 0.02%

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.6 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N 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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.8 1.4 [email protected]

Weakness enumeration for CVE-2025-27613

OS Trackers for CVE-2025-27613

vendor priority summary link
alpine low CVE-2025-27613: 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-27613
debian not yet assigned CVE-2025-27613 not yet assigned 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-27613
gentoo high CVE-2025-27613: 1 GLSA(s) (202507-09), 1 atom(s) (dev-vcs/git); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-27613
redhat medium https://access.redhat.com/security/cve/CVE-2025-27613
suse medium CVE-2025-27613 severity moderate: SUSE including 146 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, …), 389 product×package rows across 51 product lines (Container bci/kiwi, Container bci/spack, … (51 product lines)): Fixed 331, Known Not Affected 58. https://www.suse.com/security/cve/CVE-2025-27613/
ubuntu medium CVE-2025-27613 medium priority: Ubuntu including 1 source packages (git), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, upstream, xenial): released 8. https://ubuntu.com/security/CVE-2025-27613

Affected software / configurations for CVE-2025-27613

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-27613

cvelogic Threat Intelligence