Weakforced 2.x — End of Life
EOLWeakforced 2.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 2.12 | Aug 23, 2024 | — | Aug 20, 2025 | 2.12.1 | EOL |
| 2.10 | Dec 5, 2023 | — | Aug 23, 2024 | 2.10.3 | EOL |
| 2.8 | Dec 5, 2022 | — | Dec 20, 2023 | 2.8.0 | EOL |
| 2.6 | Nov 24, 2021 | — | Dec 5, 2022 | 2.6.2 | EOL |
| 2.4 | Aug 5, 2020 | — | Nov 24, 2021 | 2.4.1 | EOL |
| 2.2 | Nov 7, 2019 | — | Aug 5, 2020 | 2.2.2 | EOL |
| 2.0 | Dec 11, 2018 | — | Nov 25, 2019 | 2.0.1 | EOL |
CVEs affecting Weakforced 2.x (0)
Weakforced 2.x is EOL — migrate to Weakforced 3.x
Weakforced 3.x is the next major release. Plan your upgrade before Weakforced 2.x stops receiving security patches.
Frequently asked questions
Is Weakforced 2 end of life?
Yes. All Weakforced 2.x releases have reached end of life and no longer receive security patches. Migrate to Weakforced 3.x as soon as possible.
What CVEs affect Weakforced 2?
No CVEs are currently tracked for Weakforced 2.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.
What is the latest Weakforced 2 version?
The latest Weakforced 2.x patch release is 2.12.1, released on February 11, 2025. Always run the latest patch to benefit from all security fixes.
How to migrate from Weakforced 2 to Weakforced 3?
To migrate from Weakforced 2 to Weakforced 3: (1) review the official Weakforced 3 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.
Is it safe to run Weakforced 2 in production?
No. Weakforced 2 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA