Visual Cobol · Lifecycle Status

Visual Cobol End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Visual Cobol versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Visual Cobol 8.0 reaches end of life on July 31, 2026. Plan your migration now — 83 days remaining.
Latest Active
9.0
9.0 series
Next EOL
8.0
Jul 31, 2026
Active Versions
2
of 12 total
EOL Versions
9
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 20132014201520162017201820192020202120222023202420252026202720282.02.12.22.33.04.05.06.07.08.09.010.0TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
2.0 Apr 27, 2012 Dec 31, 2014 4147 days past EOL EOL
2.1 Apr 5, 2013 May 31, 2017 3265 days past EOL EOL
2.2 Nov 19, 2014 Jul 31, 2018 2839 days past EOL EOL
2.3 Oct 3, 2016 Sep 30, 2019 2413 days past EOL EOL
3.0 Jul 7, 2017 Jul 31, 2021 1743 days past EOL EOL
4.0 Jun 14, 2018 Jun 30, 2022 1409 days past EOL EOL
5.0 Jun 21, 2019 Jun 30, 2023 1044 days past EOL EOL
6.0 Jun 18, 2020 Jun 30, 2024 678 days past EOL EOL
7.0 Sep 14, 2021 Sep 30, 2025 221 days past EOL EOL
8.0 Jul 13, 2022 Jul 31, 2026 83 days remaining Warning
9.0 Jun 29, 2023 Jul 31, 2027 448 days remaining Active
10.0 Jul 19, 2024 Jul 31, 2028 814 days remaining Active

What does Visual Cobol end of life mean for your organization?

When a Visual Cobol 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 Visual Cobol 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Visual Cobol?
The next Visual Cobol version reaching EOL is 8.0 on July 31, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Visual Cobol?
The latest active version of Visual Cobol is 9.0. Always verify against the table above as support windows can change.
What happens when Visual Cobol reaches end of life?
When Visual Cobol reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Visual Cobol?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Visual Cobol versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →