Git 2.54 · Version Status

Git 2.54 End of Life Date

Git 2.54 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ Git 2.54 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
2.54.0
Standard release
Release Date
Apr 20, 2026
Git 2.54 series
Where these dates come from
End of active supportJun 29, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
ReleaseApr 20, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Git 2.54 was released on April 20, 2026 and has no published end-of-life date yet. Its most recent patch is 2.54.0, published April 20, 2026.

← Git 2.53 All Git versions Git 2.55 →
25 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
Out of Support
15/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Git Versions
VersionLatestEOL DateStatus
2.43 2.43.6 Jan 14, 2025 EOL
2.44 2.44.3 Jan 14, 2025 EOL
2.45 2.45.4 Jul 8, 2025 EOL
2.46 2.46.4 Jul 8, 2025 EOL
2.47 2.47.3 Oct 15, 2025 EOL
2.48 2.48.2 EOL Active
2.49 2.49.1 EOL Active
2.50 2.50.1 EOL Active

What does Git 2.54 end of life mean?

When Git 2.54 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Git 2.54 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Git 2.56 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Git 2.54 reach end of life?
Git 2.54 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is Git 2.54 still supported?
Yes, Git 2.54 is currently supported. The EOL date is TBD.
What should I upgrade to from Git 2.54?
The recommended upgrade from Git 2.54 is Git 2.56 — the latest actively supported version. Check the Git full timeline for all supported versions.
What are the security risks of running Git 2.54 past EOL?
When Git 2.54 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Git should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →