PCI DSS End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all PCI DSS versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.1 | — | Apr 1, 2015 | Oct 31, 2016 | 3522 days past EOL | EOL |
| 3.2 | — | Apr 1, 2016 | Dec 31, 2018 | 2731 days past EOL | EOL |
| 3.2.1 | — | May 1, 2018 | Mar 31, 2024 | 814 days past EOL | EOL |
| 4.0 | — | Mar 31, 2022 | Dec 31, 2024 | 539 days past EOL | EOL |
| 4.0.1 | — | Jun 11, 2024 | TBD | Supported | Active |
What does PCI DSS end of life mean for your organization?
When a version of PCI DSS 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 PCI DSS 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL PCI DSS versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →