Weechat End of Life Dates
other
Developers rely on Weechat, a versatile and highly customizable chat platform, to streamline their communication and collaboration efforts. Created to address the need for a flexible and secure messaging solution, Weechat has been maintained by its dedicated community since its inception. With a focus on providing a reliable and efficient way to manage multiple chat connections, Weechat has become a go-to tool for many developers, who appreciate its ability to support various protocols and integrate with other applications seamlessly. The fact that Weechat is actively maintained and updated ensures that developers can continue to use it with confidence, knowing that any issues or vulnerabilities will be promptly addressed.
Weechat's version history spans 20 releases, with 19 of these versions having already reached their end-of-life. Currently, only one version remains actively supported, which is the latest stable version, 4.9.2. The most recent version to reach its end-of-life was 4.8, which occurred on 2026-03-29. Since there are no upcoming end-of-life dates announced, developers can continue to use the current supported version without worrying about imminent support discontinuation. This landscape indicates that the Weechat community is committed to maintaining a stable and secure environment for its users, by regularly phasing out older versions and focusing on the latest release.
The security profile of Weechat is remarkably clean, with no known Common Vulnerabilities and Exposures (CVEs) tracked to date. This means that there are no critical vulnerabilities that developers need to be concerned about, and no versions are particularly affected by security issues. As a result, developers can use Weechat with a high degree of confidence, knowing that their communications and data are secure. Given the absence of any known security vulnerabilities, developers should continue to monitor the Weechat project for any updates or announcements, and plan their upgrades accordingly to ensure they remain on a supported version, thereby minimizing any potential risks.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 4.9 | Mar 29, 2026 | — | No | — | 4.9.4 | — | Active | |
| 4.8 | Nov 30, 2025 | — | Mar 29, 2026 | 117d ago | 4.8.2 | — | EOL | |
| 4.7 | Jul 19, 2025 | — | Nov 30, 2025 | 236d ago | 4.7.2 | — | EOL | |
| 4.6 | Mar 23, 2025 | — | Jul 19, 2025 | 370d ago | 4.6.3 | — | EOL | |
| 4.5 | Dec 15, 2024 | — | Mar 23, 2025 | 488d ago | 4.5.2 | — | EOL | |
| 4.4 | Aug 17, 2024 | — | Dec 15, 2024 | 586d ago | 4.4.4 | — | EOL | |
| 4.3 | May 26, 2024 | — | Aug 17, 2024 | 706d ago | 4.3.6 | — | EOL | |
| 4.2 | Jan 21, 2024 | — | May 26, 2024 | 789d ago | 4.2.3 | — | EOL | |
| 4.1 | Oct 15, 2023 | — | Jan 21, 2024 | 915d ago | 4.1.3 | — | EOL | |
| 4.0 | Jun 24, 2023 | — | Oct 15, 2023 | 1013d ago | 4.0.8 | — | EOL | |
| 3.8 | Jan 8, 2023 | — | Jun 24, 2023 | 1126d ago | 3.8 | — | EOL | |
| 3.7 | Oct 9, 2022 | — | Jan 8, 2023 | 1293d ago | 3.7.1 | — | EOL | |
| 3.6 | Jul 10, 2022 | — | Oct 9, 2022 | 1384d ago | 3.6 | — | EOL | |
| 3.5 | Mar 27, 2022 | — | Jul 10, 2022 | 1475d ago | 3.5 | — | EOL | |
| 3.4 | Dec 18, 2021 | — | Mar 27, 2022 | 1580d ago | 3.4.1 | — | EOL | |
| 3.3 | Sep 19, 2021 | — | Dec 18, 2021 | 1679d ago | 3.3 | — | EOL | |
| 3.2 | Jun 13, 2021 | — | Sep 19, 2021 | 1769d ago | 3.2.1 | — | EOL | |
| 3.1 | Mar 7, 2021 | — | Jun 13, 2021 | 1867d ago | 3.1 | — | EOL | |
| 3.0 | Nov 11, 2020 | — | Mar 7, 2021 | 1965d ago | 3.0.1 | — | EOL | |
| 2.9 | Jul 18, 2020 | — | Nov 11, 2020 | 2081d ago | 2.9 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
