OkHttp 4 · Version Status

OkHttp 4 End of Life Date

OkHttp 4 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.

OkHttp 4 is actively supported. EOL date: August 31, 2028.
📅 Get reminded before OkHttp 4 reaches EOL on August 31, 2028 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Aug 31, 2028
709 days remaining
Latest Release
4.12.0
Standard release
Release Date
Jun 26, 2019
OkHttp 4 series
Lifecycle detail

OkHttp 4 was released on June 26, 2019 and support is scheduled to end on August 31, 2028 — a planned supported lifespan of 9 years and 2 months. Its most recent patch is 4.12.0, published October 16, 2023.

← OkHttp 3 All OkHttp versions OkHttp 5 →
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/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 OkHttp Versions
VersionLatestEOL DateStatus
3 3.14.9 Dec 31, 2021 EOL
4 4.12.0 Aug 31, 2028 Active
5 5.5.0 EOL Active

What does OkHttp 4 end of life mean?

When OkHttp 4 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 OkHttp 4 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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

Frequently Asked Questions
When does OkHttp 4 reach end of life?
OkHttp 4 reached end of life on August 31, 2028. That is 709 days remaining.
Is OkHttp 4 still supported?
Yes, OkHttp 4 is currently supported. The EOL date is August 31, 2028.
What should I upgrade to from OkHttp 4?
The recommended upgrade from OkHttp 4 is OkHttp 5 — the latest actively supported version. Check the OkHttp full timeline for all supported versions.
What are the security risks of running OkHttp 4 past EOL?
When OkHttp 4 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 OkHttp should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →