PCI DSS 3.2 · Version Status
PCI DSS 3.2 End of Life Date
PCI DSS 3.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
PCI DSS 3.2 is past end of life. This version no longer receives security patches. 2787 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 31, 2018
2787 days past EOL
Latest Release
—
Standard release
Release Date
Apr 1, 2016
PCI DSS 3.2 series
Lifecycle detail
PCI DSS 3.2 was released on April 1, 2016 and support ended on December 31, 2018 — a supported lifespan of 2 years and 9 months, in line with the 2 years and 9 months median for PCI DSS releases. It has been without security patches for 7 years and 8 months. 2 newer PCI DSS releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended PCI DSS 3.2 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 3.1 |
— |
Oct 31, 2016 |
EOL |
| → 3.2 |
— |
Dec 31, 2018 |
EOL |
| 3.2.1 |
— |
Mar 31, 2024 |
EOL |
| 4.0 |
— |
Dec 31, 2024 |
EOL |
| 4.0.1 |
— |
EOL |
Active |
What does PCI DSS 3.2 end of life mean?
When PCI DSS 3.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running PCI DSS 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to PCI DSS 4.0.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does PCI DSS 3.2 reach end of life?
PCI DSS 3.2 reached end of life on December 31, 2018. This version is no longer receiving security patches.
Is PCI DSS 3.2 still supported?
No. PCI DSS 3.2 reached end of life on December 31, 2018 and is no longer receiving security patches.
What should I upgrade to from PCI DSS 3.2?
The recommended upgrade from PCI DSS 3.2 is
PCI DSS 4.0.1 — the latest actively supported version. Check the
PCI DSS full timeline for all supported versions.
What are the security risks of running PCI DSS 3.2 past EOL?
When PCI DSS 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL PCI DSS should migrate immediately or implement compensating controls.