Complete end-of-life dates, support windows, and security status for all Weechat versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.9 | 2.9 | Jul 18, 2020 | Nov 11, 2020 | 2005 days past EOL | EOL |
| 3.0 | 3.0.1 | Nov 11, 2020 | Mar 7, 2021 | 1889 days past EOL | EOL |
| 3.1 | 3.1 | Mar 7, 2021 | Jun 13, 2021 | 1791 days past EOL | EOL |
| 3.2 | 3.2.1 | Jun 13, 2021 | Sep 19, 2021 | 1693 days past EOL | EOL |
| 3.3 | 3.3 | Sep 19, 2021 | Dec 18, 2021 | 1603 days past EOL | EOL |
| 3.4 | 3.4.1 | Dec 18, 2021 | Mar 27, 2022 | 1504 days past EOL | EOL |
| 3.5 | 3.5 | Mar 27, 2022 | Jul 10, 2022 | 1399 days past EOL | EOL |
| 3.6 | 3.6 | Jul 10, 2022 | Oct 9, 2022 | 1308 days past EOL | EOL |
| 3.7 | 3.7.1 | Oct 9, 2022 | Jan 8, 2023 | 1217 days past EOL | EOL |
| 3.8 | 3.8 | Jan 8, 2023 | Jun 24, 2023 | 1050 days past EOL | EOL |
| 4.0 | 4.0.8 | Jun 24, 2023 | Oct 15, 2023 | 937 days past EOL | EOL |
| 4.1 | 4.1.3 | Oct 15, 2023 | Jan 21, 2024 | 839 days past EOL | EOL |
| 4.2 | 4.2.3 | Jan 21, 2024 | May 26, 2024 | 713 days past EOL | EOL |
| 4.3 | 4.3.6 | May 26, 2024 | Aug 17, 2024 | 630 days past EOL | EOL |
| 4.4 | 4.4.4 | Aug 17, 2024 | Dec 15, 2024 | 510 days past EOL | EOL |
| 4.5 | 4.5.2 | Dec 15, 2024 | Mar 23, 2025 | 412 days past EOL | EOL |
| 4.6 | 4.6.3 | Mar 23, 2025 | Jul 19, 2025 | 294 days past EOL | EOL |
| 4.7 | 4.7.2 | Jul 19, 2025 | Nov 30, 2025 | 160 days past EOL | EOL |
| 4.8 | 4.8.2 | Nov 30, 2025 | Mar 29, 2026 | 41 days past EOL | EOL |
| 4.9 | 4.9.0 | Mar 29, 2026 | Already EOL | Supported | Active |
When a Weechat version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Weechat should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →