Visual Cobol End of Life Dates
other
Developers relying on Visual Cobol for their applications need to stay informed about the lifecycle of this product to ensure timely upgrades and mitigate potential security risks. Created to address the needs of developers working with COBOL, Visual Cobol has been maintained to provide a platform for building and deploying COBOL applications. With its rich history, Visual Cobol has become a crucial tool for many development teams, offering a way to modernize legacy systems and integrate them with newer technologies. The maintenance of Visual Cobol is a testament to its importance in the development community, with efforts focused on supporting developers who continue to use this technology.
The end-of-life landscape for Visual Cobol is characterized by a total of 12 versions, out of which 9 have already reached their end-of-life, leaving 3 versions that are still supported. The next significant milestone is the end-of-life date for version 8.0, scheduled for July 31, 2026. This follows the end-of-life of version 7.0, which occurred on September 30, 2025. Understanding these timelines is essential for planning and executing upgrades, ensuring that applications remain supported and secure. By tracking these dates, developers can avoid the risks associated with using unsupported software, including the lack of security patches and technical support.
The security outlook for Visual Cobol is currently favorable, with no recorded Common Vulnerabilities and Exposures (CVEs), indicating a low risk profile for this product. This means that there are no critical vulnerabilities to address, and no version is particularly affected. As a result, developers using Visual Cobol do not need to take immediate action to patch vulnerabilities. However, it is still crucial to keep an eye on future updates and plan for upgrades to ensure continued support and to mitigate any potential future security risks. Given the upcoming end-of-life date for version 8.0, developers should start evaluating their options for migrating to a supported version to maintain the security and integrity of their applications.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 10.0 | Jul 19, 2024 | — | Jul 31, 2028 | in 738d | — | — | Active | |
| 9.0 | Jun 29, 2023 | — | Jul 31, 2027 | in 372d | — | — | Active | |
| 8.0 | Jul 13, 2022 | — | Jul 31, 2026 | in 7d | — | — | EOL soon | |
| 7.0 | Sep 14, 2021 | — | Sep 30, 2025 | 297d ago | — | — | EOL | |
| 6.0 | Jun 18, 2020 | — | Jun 30, 2024 | 754d ago | — | — | EOL | |
| 5.0 | Jun 21, 2019 | — | Jun 30, 2023 | 1120d ago | — | — | EOL | |
| 4.0 | Jun 14, 2018 | — | Jun 30, 2022 | 1485d ago | — | — | EOL | |
| 3.0 | Jul 7, 2017 | — | Jul 31, 2021 | 1819d ago | — | — | EOL | |
| 2.3 | Oct 3, 2016 | — | Sep 30, 2019 | 2489d ago | — | — | EOL | |
| 2.2 | Nov 19, 2014 | — | Jul 31, 2018 | 2915d ago | — | — | EOL | |
| 2.1 | Apr 5, 2013 | — | May 31, 2017 | 3341d ago | — | — | EOL | |
| 2.0 | Apr 27, 2012 | — | Dec 31, 2014 | 4223d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
