Quarkus 1 · Version Status
Quarkus 1 End of Life Date
Quarkus 1 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.
⚠
Quarkus 1 is past end of life. This version no longer receives security patches. 1956 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 30, 2021
1956 days past EOL
Latest Release
1.13.7
Standard release
Release Date
Nov 25, 2019
Quarkus 1 series
Extended Support
Nov 20, 2021
Red Hat build of Quarkus · paid · ended
Where these dates come from
End of lifeJun 30, 2021Vendor's own page (our correction) · quarkus.io · checked Oct 11, 2026medium · 1 source agrees End of extended supportNov 20, 2021endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseNov 25, 2019endoflife.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.
Lifecycle detail
Quarkus 1 was released on November 25, 2019 and support ended on June 30, 2021 — a supported lifespan of 1 year and 7 months, longer than the 35 days median for Quarkus releases. It was not an LTS release; Quarkus reserves longer patch windows for its LTS releases. Its latest release on record is 1.13.7, published June 9, 2021 — 21 days before support ended. It has been past its end-of-life date for 5 years and 4 months. 57 newer Quarkus releases have shipped since.
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 |
|---|
| 0 |
0.28.1 |
Nov 25, 2019 |
EOL |
| → 1 |
1.13.7 |
Jun 30, 2021 |
EOL |
| 2.0 |
2.0.3 |
Jul 22, 2021 |
EOL |
| 2.1 |
2.1.4 |
Aug 26, 2021 |
EOL |
| 2.2 |
2.2.5 |
Dec 21, 2021 |
EOL |
| 2.3 |
2.3.1 |
Oct 20, 2021 |
EOL |
| 2.4 |
2.4.2 |
Nov 17, 2021 |
EOL |
| 2.5 |
2.5.4 |
Dec 17, 2021 |
EOL |
What does Quarkus 1 end of life mean?
When Quarkus 1 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 Quarkus 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Quarkus 3.40 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Quarkus 1 reach end of life?
Quarkus 1 reached end of life on June 30, 2021. This version is no longer receiving security patches.
Is Quarkus 1 still supported?
No. Quarkus 1 reached end of life on June 30, 2021 and is no longer receiving security patches.
What should I upgrade to from Quarkus 1?
The recommended upgrade from Quarkus 1 is
Quarkus 3.40 — the latest actively supported version. Check the
Quarkus full timeline for all supported versions.
What are the security risks of running Quarkus 1 past EOL?
Since Quarkus 1 reached end of life, the maintainers no longer issue 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 Quarkus should migrate immediately or implement compensating controls.