Behat 3 · Version Status
Behat 3 End of Life Date
Behat 3 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.
✓
Behat 3 is actively supported. EOL date: September 30, 2028.
📅 Get reminded before Behat 3 reaches EOL on September 30, 2028 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Sep 30, 2028
693 days remaining
Latest Release
3.34.0
Standard release
Release Date
Apr 20, 2014
Behat 3 series
Where these dates come from
End of lifeSep 30, 2028endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportSep 30, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseApr 20, 2014endoflife.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
Behat 3 was released on April 20, 2014 and support is scheduled to end on September 30, 2028 — a planned supported lifespan of 14 years and 6 months. Its most recent patch is 3.34.0, published September 27, 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 |
|---|
| 2 |
2.5.5 |
Jun 30, 2015 |
EOL |
| → 3 |
3.34.0 |
Sep 30, 2028 |
Active |
| 4 |
4.0.0 |
EOL |
Active |
What does Behat 3 end of life mean?
When Behat 3 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 Behat 3 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Behat 4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Behat 3 reach end of life?
Behat 3 reaches end of life on September 30, 2028. That is 693 days remaining.
Is Behat 3 still supported?
Yes, Behat 3 is currently supported. The EOL date is September 30, 2028.
What should I upgrade to from Behat 3?
The recommended upgrade from Behat 3 is
Behat 4 — the latest actively supported version. Check the
Behat full timeline for all supported versions.
What are the security risks of running Behat 3 past EOL?
When Behat 3 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 Behat should migrate immediately or implement compensating controls.