Microsoft JDBC Driver for SQL Server 11.2 · Version Status
Microsoft JDBC Driver for SQL Server 11.2 End of Life Date
Microsoft JDBC Driver for SQL Server 11.2 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (learn.microsoft.com); the source of each date is on the product page.
✓
Microsoft JDBC Driver for SQL Server 11.2 is actively supported. EOL date: August 4, 2027.
📅 Get reminded before Microsoft JDBC Driver for SQL Server 11.2 reaches EOL on August 4, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Aug 4, 2027
289 days remaining
Latest Release
11.2.4
Standard release
Release Date
Aug 9, 2022
Microsoft JDBC Driver for SQL Server 11.2 series
Where these dates come from
End of lifeAug 4, 2027Vendor's own page, checked by a person · learn.microsoft.com · checked Oct 19, 2026high · 2 sources agree End of active supportAug 4, 2027Vendor's own page, checked by a person · learn.microsoft.com · checked Oct 19, 2026high · 2 sources agree ReleaseAug 9, 2022Vendor's own page, checked by a person · learn.microsoft.com · checked Oct 19, 2026high · 2 sources agree 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.
Lifecycle detail
Microsoft JDBC Driver for SQL Server 11.2 was released on August 9, 2022 and support is scheduled to end on August 4, 2027 — a planned supported lifespan of 5 years, in line with the 5 years median for Microsoft JDBC Driver for SQL Server releases. Its most recent patch is 11.2.4, published October 13, 2025.
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 Microsoft JDBC Driver for SQL Server Versions
| Version | Latest | EOL Date | Status |
|---|
| 4.0 |
— |
Mar 6, 2017 |
EOL |
| 4.1 |
— |
Dec 12, 2019 |
EOL |
| 4.2 |
— |
Aug 24, 2020 |
EOL |
| 6.0 |
— |
Jul 14, 2021 |
EOL |
| 6.2 |
6.2.2 |
Jun 30, 2022 |
EOL |
| 6.4 |
6.4.0 |
Feb 27, 2023 |
EOL |
| 7.0 |
7.0.0 |
Jul 31, 2023 |
EOL |
| 7.2 |
7.2.2 |
Jan 31, 2024 |
EOL |
What does Microsoft JDBC Driver for SQL Server 11.2 end of life mean?
When Microsoft JDBC Driver for SQL Server 11.2 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 Microsoft JDBC Driver for SQL Server 11.2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Microsoft JDBC Driver for SQL Server 13.6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Microsoft JDBC Driver for SQL Server 11.2 reach end of life?
Microsoft JDBC Driver for SQL Server 11.2 reaches end of life on August 4, 2027. That is 289 days remaining.
Is Microsoft JDBC Driver for SQL Server 11.2 still supported?
Yes, Microsoft JDBC Driver for SQL Server 11.2 is currently supported. The EOL date is August 4, 2027.
What should I upgrade to from Microsoft JDBC Driver for SQL Server 11.2?
What are the security risks of running Microsoft JDBC Driver for SQL Server 11.2 past EOL?
When Microsoft JDBC Driver for SQL Server 11.2 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 Microsoft JDBC Driver for SQL Server should migrate immediately or implement compensating controls.