Oracle PeopleSoft SA/CR 8.0 End of Life Date
Oracle PeopleSoft SA/CR 8.0 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
It has been without security patches for 18 years and 1 month.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → SA/CR 8.0 | 8.0 | Aug 31, 2008 | EOL |
| Portal Solutions 8.4 | 8.4 | Mar 31, 2007 | EOL |
| Portal Solutions 8.8 | 8.8 | Mar 31, 2008 | EOL |
| Portal Solutions 8.9 | 8.9 | Mar 31, 2010 | EOL |
| Portal Solutions 9.0 | 9.0 | Oct 31, 2011 | EOL |
| EPM 8.3 | 8.3 | Dec 31, 2006 | EOL |
| EPM 8.8 | 8.8 | Dec 31, 2007 | EOL |
| EPM 8.9 | 8.9 | Apr 30, 2010 | EOL |
What does Oracle PeopleSoft SA/CR 8.0 end of life mean?
When Oracle PeopleSoft SA/CR 8.0 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Oracle PeopleSoft SA/CR 8.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Oracle PeopleSoft HCM 9.2 (Continuous Innovation) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.