CVE-2025-27613
published 2025-07-10CVE-2025-27613: 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…
PriorityP414low3.6CVSS 3.1
AVLACLPRNUIRSCCNILAN
EPSS
0.29%
20.9th percentile
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.
Affected
32 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | git | < git 1:2.39.5-0+deb12u3 (bookworm) | git 1:2.39.5-0+deb12u3 (bookworm) |
| git | git | >= 0 < 1:2.30.2-1+deb11u5 | 1:2.30.2-1+deb11u5 |
| git | git | >= 0 < 1:2.39.5-0+deb12u3 | 1:2.39.5-0+deb12u3 |
| git | git | >= 0 < 1:2.47.3-0+deb13u1 | 1:2.47.3-0+deb13u1 |
| git | git | >= 0 < 1:2.50.1-0.1 | 1:2.50.1-0.1 |
| git | git | >= 0 < 1:2.34.1-1ubuntu1.14 | 1:2.34.1-1ubuntu1.14 |
| git | git | >= 0 < 1:2.34.1-1ubuntu1.15 | 1:2.34.1-1ubuntu1.15 |
| git | git | >= 0 < 1:2.34.1-1ubuntu1.13 | 1:2.34.1-1ubuntu1.13 |
| git | git | >= 0 < 1:2.43.0-1ubuntu7.3 | 1:2.43.0-1ubuntu7.3 |
| git | git | >= 0 < 1:2.7.4-0ubuntu1.10+esm10 | 1:2.7.4-0ubuntu1.10+esm10 |
| git | git | >= 0 < 1:2.7.4-0ubuntu1.10+esm11 | 1:2.7.4-0ubuntu1.10+esm11 |
| git | git | >= 0 < 1:2.7.4-0ubuntu1.10+esm9 | 1:2.7.4-0ubuntu1.10+esm9 |
| git | git | >= 0 < 1:2.17.1-1ubuntu0.18+esm3 | 1:2.17.1-1ubuntu0.18+esm3 |
| git | git | >= 0 < 1:2.17.1-1ubuntu0.18+esm4 | 1:2.17.1-1ubuntu0.18+esm4 |
| git | git | >= 0 < 1:2.17.1-1ubuntu0.18+esm2 | 1:2.17.1-1ubuntu0.18+esm2 |
| git | git | >= 0 < 1:2.25.1-1ubuntu3.14+esm2 | 1:2.25.1-1ubuntu3.14+esm2 |
| git | git | >= 0 < 1:2.25.1-1ubuntu3.14+esm3 | 1:2.25.1-1ubuntu3.14+esm3 |
| git | git | >= 0 < 1:2.25.1-1ubuntu3.14+esm1 | 1:2.25.1-1ubuntu3.14+esm1 |
| j6t | gitk | — | — |
| j6t | gitk | — | — |
| j6t | gitk | — | — |
| j6t | gitk | — | — |
| j6t | gitk | — | — |
| j6t | gitk | — | — |
| j6t | gitk | — | — |
CVSS provenance
nvdv3.13.6LOWCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N
osv3.6LOW
vendor_debian3.6LOW
vendor_msrc3.6LOW
vendor_redhat3.6LOW
vendor_ubuntu3.6LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Git regression
vendor_ubuntu·2025-07-10·CVSS 3.6
CVE-2025-27613 [LOW] Git regression
Title: Git regression
Summary: USN-7626-1 introduced a regression in Git
USN-7626-1 fixed vulnerabilities in Git. The updates for CVE-2025-27613
and CVE-2025-46835 caused Gitk and Git GUI to not work properly on Ubuntu
16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS, and
were disabled in USN-7626-2. The problematic updates for the
aforementioned CVEs have now been corrected and reinstated in this update.
We apologize for the inconvenience.
Original advisory details:
Avi Halachmi discovered that Git incorrectly managed file modification
constraints with Gitk. An attacker could possibly use this issue to create
or write to arbitrary files on the system. (CVE-2025-27613)
Avi Halachmi discovered that Git incorrectly handled arguments when
invoking the Gitk utility. If
Ubuntu
Git regression
vendor_ubuntu·2025-07-09·CVSS 3.6
CVE-2025-27613 [LOW] Git regression
Title: Git regression
Summary: USN-7626-1 introduced a regression in Git.
USN-7626-1 fixed vulnerabilities in Git. The update introduced a regression
in gitk and git-gui. This update reverts the corresponding fixes for
CVE-2025-27613 and CVE-2025-46835 pending further investigation.
We apologize for the inconvenience.
Original advisory details:
Avi Halachmi discovered that Git incorrectly managed file modification
constraints with Gitk. An attacker could possibly use this issue to create
or write to arbitrary files on the system. (CVE-2025-27613)
Avi Halachmi discovered that Git incorrectly handled arguments when
invoking the Gitk utility. If a user were tricked into cloning a malicious
Git repository, an attacker could possibly use this issue to run arbitrary
commands. This issue on
Ubuntu
Git vulnerabilities
vendor_ubuntu·2025-07-08·CVSS 3.6
CVE-2025-46835 [LOW] Git vulnerabilities
Title: Git vulnerabilities
Summary: Several security issues were fixed in Git.
Avi Halachmi discovered that Git incorrectly managed file modification
constraints with Gitk. An attacker could possibly use this issue to create
or write to arbitrary files on the system. (CVE-2025-27613)
Avi Halachmi discovered that Git incorrectly handled arguments when
invoking the Gitk utility. If a user were tricked into cloning a malicious
Git repository, an attacker could possibly use this issue to run arbitrary
commands. This issue only affected Ubuntu 24.04 LTS, Ubuntu 24.10, and
Ubuntu 25.04. (CVE-2025-27614)
Johannes Sixt discovered that Git incorrectly managed file modification
constraints with Git GUI. If a user were tricked into editing a file in a
malicious Git repository, an attacker could p
Microsoft
GitHub: CVE-2025-27613 Gitk Arguments Vulnerability
vendor_msrc·2025-07-08·CVSS 3.6
CVE-2025-27613 [LOW] GitHub: CVE-2025-27613 Gitk Arguments Vulnerability
GitHub: CVE-2025-27613 Gitk Arguments Vulnerability
Description: CVE-2025-27613 is regarding a vulnerability in Gitk where when a user clones an untrusted repository and runs Gitk without additional command arguments, any writable file can be created and truncated. The option "Support per-file encoding" must have been enabled. The operation "Show origin of this line" is affected as well, regardless of the option being enabled or not. GitHub created this CVE on their behalf. The documented Visual Studio updates incorporate updates in GitK which address this vulnerability.
Please see CVE-2025-27613 for more information.
Visual Studio: Visual Studio
Github: Github
Customer Action Required: Yes
Remediation: Release Notes
Reference: https://my.visualstudio.com/Downloads?q=Visual Studio 20
Red Hat
gitk: Git file creation flaw
vendor_redhat·2025-07-08·CVSS 3.6
CVE-2025-27613 [LOW] CWE-73 gitk: Git file creation flaw
gitk: Git file creation flaw
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.
A vulnerability has been identified in the gitk application that could lead to unauthorized file modification or data loss.
This flaw manifests in two primary scenar
Debian
CVE-2025-27613: git - Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clo...
vendor_debian·2025·CVSS 3.6
CVE-2025-27613 [LOW] CVE-2025-27613: git - Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clo...
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.
Scope: local
bookworm: resolved (fixed in 1:2.39.5-0+deb12u3)
bullseye: resolved (fixed in 1:2.30.2-1+deb11u5)
forky: resolved (fixed in 1:2.50.1-0.1)
sid: resolved (fixed in 1:2.50.1-0.1)
trixie:
OSV
CVE-2025-27613: Gitk is a Tcl/Tk based Git history browser
osv·2025-07-10·CVSS 3.6
CVE-2025-27613 [LOW] CVE-2025-27613: Gitk is a Tcl/Tk based Git history browser
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.
OSV
git regression
osv·2025-07-10·CVSS 3.6
CVE-2025-27613 [LOW] git regression
git regression
USN-7626-1 fixed vulnerabilities in Git. The updates for CVE-2025-27613
and CVE-2025-46835 caused Gitk and Git GUI to not work properly on Ubuntu
16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS, and
were disabled in USN-7626-2. The problematic updates for the
aforementioned CVEs have now been corrected and reinstated in this update.
We apologize for the inconvenience.
Original advisory details:
Avi Halachmi discovered that Git incorrectly managed file modification
constraints with Gitk. An attacker could possibly use this issue to create
or write to arbitrary files on the system. (CVE-2025-27613)
Avi Halachmi discovered that Git incorrectly handled arguments when
invoking the Gitk utility. If a user were tricked into cloning a malicious
Git repositor
OSV
git regression
osv·2025-07-09·CVSS 3.6
CVE-2025-27613 [LOW] git regression
git regression
USN-7626-1 fixed vulnerabilities in Git. The update introduced a regression
in gitk and git-gui. This update reverts the corresponding fixes for
CVE-2025-27613 and CVE-2025-46835 pending further investigation.
We apologize for the inconvenience.
Original advisory details:
Avi Halachmi discovered that Git incorrectly managed file modification
constraints with Gitk. An attacker could possibly use this issue to create
or write to arbitrary files on the system. (CVE-2025-27613)
Avi Halachmi discovered that Git incorrectly handled arguments when
invoking the Gitk utility. If a user were tricked into cloning a malicious
Git repository, an attacker could possibly use this issue to run arbitrary
commands. This issue only affected Ubuntu 24.04 LTS, Ubuntu 24.10, and
Ubuntu 25.04
OSV
git vulnerabilities
osv·2025-07-08·CVSS 3.6
CVE-2025-27613 [LOW] git vulnerabilities
git vulnerabilities
Avi Halachmi discovered that Git incorrectly managed file modification
constraints with Gitk. An attacker could possibly use this issue to create
or write to arbitrary files on the system. (CVE-2025-27613)
Avi Halachmi discovered that Git incorrectly handled arguments when
invoking the Gitk utility. If a user were tricked into cloning a malicious
Git repository, an attacker could possibly use this issue to run arbitrary
commands. This issue only affected Ubuntu 24.04 LTS, Ubuntu 24.10, and
Ubuntu 25.04. (CVE-2025-27614)
Johannes Sixt discovered that Git incorrectly managed file modification
constraints with Git GUI. If a user were tricked into editing a file in a
malicious Git repository, an attacker could possibly use this issue to
create or write to arbitrary files
No detection rules found.
No public exploits indexed.
https://github.com/j6t/gitk/compare/465f03869ae11acd04abfa1b83c67879c867410c..026c397d911cde55924d7eb1311d0fd6e2e105d5https://github.com/j6t/gitk/compare/7dd272eca153058da2e8d5b9960bbbf0b4f0cbaa..67a128b91e25978a15f9f7e194d81b441d603652https://github.com/j6t/gitk/security/advisories/GHSA-f3cw-xrj3-wr2vhttp://www.openwall.com/lists/oss-security/2025/07/08/4https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
2025-07-10
Published