HtmlUnit 1 · Version Status
HtmlUnit 1 End of Life Date
HtmlUnit 1 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (htmlunit.org); the source of each date is on the product page.
⚠
HtmlUnit 1 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
1.14
Standard release
Release Date
May 22, 2002
HtmlUnit 1 series
Where these dates come from
ReleaseMay 22, 2002Our catalog, built from the vendor pages · htmlunit.orgmedium · 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
HtmlUnit 1 was released on May 22, 2002. Its most recent patch is 1.14, published January 9, 2008.
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 |
|---|
| → 1 |
1.14 |
Supported |
EOL |
| 2 |
2.70.0 |
Supported |
EOL |
| 3 |
3.11.0 |
Supported |
EOL |
| 4 |
4.21.0 |
Supported |
EOL |
| 5 |
5.7.0 |
EOL |
Active |
What does HtmlUnit 1 end of life mean?
When HtmlUnit 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 HtmlUnit 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to HtmlUnit 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does HtmlUnit 1 reach end of life?
HtmlUnit 1 has already reached end of life, though the vendor has not published an exact date.
Is HtmlUnit 1 still supported?
No. HtmlUnit 1 reached end of life on an unpublished date and is no longer receiving security patches.
What should I upgrade to from HtmlUnit 1?
The recommended upgrade from HtmlUnit 1 is
HtmlUnit 5 — the latest actively supported version. Check the
HtmlUnit full timeline for all supported versions.
What are the security risks of running HtmlUnit 1 past EOL?
Since HtmlUnit 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 HtmlUnit should migrate immediately or implement compensating controls.