From 914f1052d7f2860c2f9f6e4db49698f7a8e982a0 Mon Sep 17 00:00:00 2001 From: Johannes Schindelin Date: Fri, 17 Apr 2026 03:02:16 +0200 Subject: [PATCH] FAQ: recommend to upgrade at least to v2.53.0(3) v2.53.0(3) addressed CVE-2026-32631, and v2.53.0(2) addressed CVE-2025-66413 Signed-off-by: Johannes Schindelin --- content/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/faq.md b/content/faq.md index c0a0862..e7c7263 100644 --- a/content/faq.md +++ b/content/faq.md @@ -40,7 +40,7 @@ In the meantime you could try: In general, yes: it is a good idea to stay up-to-date. -If you have a version older than 2.51.1, it is *highly* advisable to upgrade. A couple of Git versions came with important fixes to security-relevant vulnerabilities: 2.51.1, 2.50.1, 2.47.1(2), 2.45.1, 2.40.1, 2.39.2, 2.39.1, 2.38.1, 2.37.1, 2.36.0, 2.35.3, 2.35.3, 2.30.2, 2.30.0(2), 2.29.2(3), 2.29.2(2), 2.26.1, 2.24.1(2), 2.17.1(2), 2.14.1, 2.7.4, 2.7.0, 2.6.1, 2.5.2, 1.9.5-preview20150319, and 1.9.5-preview20141217. +If you have a version older than 2.53.0(3), it is *highly* advisable to upgrade. A couple of Git versions came with important fixes to security-relevant vulnerabilities: 2.53.0(3), 2.53.0(2), 2.51.1, 2.50.1, 2.47.1(2), 2.45.1, 2.40.1, 2.39.2, 2.39.1, 2.38.1, 2.37.1, 2.36.0, 2.35.3, 2.35.3, 2.30.2, 2.30.0(2), 2.29.2(3), 2.29.2(2), 2.26.1, 2.24.1(2), 2.17.1(2), 2.14.1, 2.7.4, 2.7.0, 2.6.1, 2.5.2, 1.9.5-preview20150319, and 1.9.5-preview20141217. ## How do I update *Git for Windows* upon new releases?