Samba 4.25 · Version Status
Samba 4.25 End of Life Date
Samba 4.25 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.
✓
Samba 4.25 is actively supported. EOL date: March 31, 2028.
📅 Get reminded before Samba 4.25 reaches EOL on March 31, 2028 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Mar 31, 2028
550 days remaining
Latest Release
4.25.0
Standard release
Release Date
Sep 24, 2026
Samba 4.25 series
Lifecycle detail
Samba 4.25 was released on September 24, 2026 and support is scheduled to end on March 31, 2028 — a planned supported lifespan of 1 year and 6 months, in line with the 1 year and 6 months median for Samba releases. Its most recent patch is 4.25.0, published September 24, 2026.
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 →
| Version | Latest | EOL Date | Status |
|---|
| 3.0 |
3.0.37 |
Aug 5, 2009 |
EOL |
| 3.2 |
3.2.15 |
Mar 1, 2010 |
EOL |
| 3.3 |
3.3.16 |
Aug 9, 2011 |
EOL |
| 3.4 |
3.4.17 |
Dec 11, 2012 |
EOL |
| 3.5 |
3.5.22 |
Oct 11, 2013 |
EOL |
| 3.6 |
3.6.25 |
Mar 4, 2015 |
EOL |
| 4.0 |
4.0.26 |
Sep 8, 2015 |
EOL |
| 4.1 |
4.1.23 |
Mar 22, 2016 |
EOL |
What does Samba 4.25 end of life mean?
When Samba 4.25 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 Samba 4.25 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Samba 4.25 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Samba 4.25 reach end of life?
Samba 4.25 reached end of life on March 31, 2028. That is 550 days remaining.
Is Samba 4.25 still supported?
Yes, Samba 4.25 is currently supported. The EOL date is March 31, 2028.
What should I upgrade to from Samba 4.25?
The recommended upgrade from Samba 4.25 is
Samba 4.25 — the latest actively supported version. Check the
Samba full timeline for all supported versions.
What are the security risks of running Samba 4.25 past EOL?
When Samba 4.25 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 Samba should migrate immediately or implement compensating controls.