CVE-2025-27614

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 10, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Sep 1, 2026
Patch available. Sources: github_commit, github.
generic

oss-security - Multiple vulnerabilities fixed in Git

http://www.openwall.com/lists/oss-security/2025/07/08/4
github Patch Available

Arbitrary command execution with Gitk · Advisory · j6t/gitk · GitHub

https://github.com/j6t/gitk/security/advisories/GHSA-g4v5-fjv9-mhhc
github_commit

commit 8e3070aa5e33 (j6t/gitk)

Fix landed in j6t/gitk commit 8e3070aa5e33 — awaiting tagged release

https://github.com/j6t/gitk/commit/8e3070aa5e331be45d4d03e3be41f84494fce129

Vendor Advisories for CVE-2025-27614(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugitweb (1:2.17.1-1ubuntu0.18+esm2) @ bionic2026-05-21ubuntu
redhatgit-0:2.43.7-1.el8_102025-07-23redhat
redhatgit-0:2.47.3-1.el10_02025-07-22redhat
redhatgit-0:2.47.3-1.el9_62025-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
git—2.43.7-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
git—2.45.4-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
git—2.47.3-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
git—2.49.1-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
git—2.50.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
git—2.50.1-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
git1:2.47.2-0.21:2.47.3-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
git1:2.47.2-0.2 ... 1:2.50.0~rc0+next.20250528-1 (9 versions)1:2.50.1-0.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 181 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 22:06 UTCOSV refresh
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:13 UTCEPSS rescore
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-11 09:35 UTCEPSS rescore
  9. 2026-09-10 09:33 UTCEPSS rescore
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-06 13:46 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-04 05:05 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-08-30 19:16 UTCEPSS rescore
  18. 2026-08-30 19:16 UTCEPSS rescore
  19. 2026-08-30 01:21 UTCEPSS rescore
  20. 2026-08-28 22:13 UTCOSV refresh
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-24 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:18 UTCEPSS rescore
  2. 2026-08-21 23:48 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:47 UTCEPSS rescore
  5. 2026-08-17 13:46 UTCEPSS rescore
  6. 2026-08-16 14:55 UTCEPSS rescore
  7. 2026-08-16 02:13 UTCEPSS rescore
  8. 2026-08-15 01:29 UTCEPSS rescore
  9. 2026-08-13 21:59 UTCEPSS rescore
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-12 09:54 UTCOSV refresh
  12. 2026-08-10 23:59 UTCEPSS rescore
  13. 2026-08-09 13:45 UTCEPSS rescore
  14. 2026-08-07 16:26 UTCEPSS rescore
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-05 19:16 UTCEPSS rescore
  17. 2026-08-04 15:09 UTCEPSS rescore
  18. 2026-08-04 10:37 UTCEPSS rescore
  19. 2026-08-03 10:35 UTCEPSS rescore
  20. 2026-08-02 02:26 UTCEPSS rescore
  21. 2026-08-01 04:15 UTCEPSS rescore
  22. 2026-07-30 16:27 UTCEPSS rescore
  23. 2026-07-30 01:29 UTCEPSS rescore
  24. 2026-07-28 15:35 UTCEPSS rescore
  25. 2026-07-27 16:57 UTCOSV refresh
  26. 2026-07-27 14:12 UTCEPSS rescore
  27. 2026-07-26 14:53 UTCEPSS rescore
  28. 2026-07-25 14:17 UTCEPSS rescore
  29. 2026-07-24 14:17 UTCEPSS rescore
  30. 2026-07-23 02:52 UTCEG score recompute
  31. 2026-07-22 14:07 UTCEPSS rescore
  32. 2026-07-22 14:07 UTCEPSS rescore
  33. 2026-07-21 15:24 UTCEPSS rescore
  34. 2026-07-21 15:24 UTCEPSS rescore
  35. 2026-07-20 17:07 UTCEPSS rescore
  36. 2026-07-19 14:30 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-19 02:28 UTCEPSS rescore
  39. 2026-07-19 02:28 UTCEPSS rescore
  40. 2026-07-18 10:04 UTCEPSS rescore
  41. 2026-07-18 10:04 UTCEPSS rescore
  42. 2026-07-16 17:02 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 01:59 UTCEPSS rescore
  46. 2026-07-15 01:59 UTCEPSS rescore
  47. 2026-07-13 22:29 UTCEPSS rescore
  48. 2026-07-13 06:12 UTCEPSS rescore
  49. 2026-07-13 06:12 UTCEPSS rescore
  50. 2026-07-12 05:46 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-11 08:27 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-10 09:52 UTCOSV refresh
  55. 2026-07-09 19:09 UTCEPSS rescore
  56. 2026-07-08 15:14 UTCEPSS rescore
  57. 2026-07-07 13:45 UTCEPSS rescore
  58. 2026-07-06 16:27 UTCEPSS rescore
  59. 2026-07-06 16:26 UTCEPSS rescore
  60. 2026-07-06 02:22 UTCEPSS rescore
  61. 2026-07-05 02:30 UTCEPSS rescore
  62. 2026-07-04 06:30 UTCEPSS rescore
  63. 2026-07-02 17:01 UTCEPSS rescore
  64. 2026-07-01 15:06 UTCEPSS rescore
  65. 2026-06-30 23:22 UTCEPSS rescore
  66. 2026-06-30 23:21 UTCEPSS rescore
  67. 2026-06-29 14:06 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 04:55 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-27 03:08 UTCEPSS rescore
  73. 2026-06-25 13:49 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-24 14:04 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-27614?
CVE-2025-27614 is a high vulnerability published on July 10, 2025. 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…
When was CVE-2025-27614 disclosed?
CVE-2025-27614 was first published in the National Vulnerability Database on July 10, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-27614 actively exploited?
CVE-2025-27614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.6% of all scored CVEs.
What is the CVSS score of CVE-2025-27614?
CVE-2025-27614 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-27614?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-27614, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-27614

Explore →

Is Your Infrastructure Affected by CVE-2025-27614?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs