Oracle PeopleSoft FMS/ESA/SCM 8.9 · Version Status

Oracle PeopleSoft FMS/ESA/SCM 8.9 End of Life Date

Oracle PeopleSoft FMS/ESA/SCM 8.9 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.

⚠ Oracle PeopleSoft FMS/ESA/SCM 8.9 is past end of life. This version no longer receives security patches. 5884 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 31, 2010
5884 days past EOL
Latest Release
8.9
Standard release
Release Date
—
Oracle PeopleSoft FMS/ESA/SCM 8.9 series
Extended Support
Aug 31, 2013
Extended support · ended
Lifecycle detail

It has been without security patches for 16 years and 1 month.

← Oracle PeopleSoft FMS/ESA/SCM 9.0 All Oracle PeopleSoft versions Oracle PeopleSoft FMS/ESA/SCM 8.8 →
70 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 →
Recommended upgrade path
Oracle PeopleSoft HCM 9.2 (Continuous Innovation)
Latest release: 55 · EOL: Supported
View full Oracle PeopleSoft timeline →
Extended Support
Extended Oracle PeopleSoft FMS/ESA/SCM 8.9 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Oracle PeopleSoft Versions
VersionLatestEOL DateStatus
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 FMS/ESA/SCM 8.9 end of life mean?

When Oracle PeopleSoft FMS/ESA/SCM 8.9 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 FMS/ESA/SCM 8.9 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.

Frequently Asked Questions
When does Oracle PeopleSoft FMS/ESA/SCM 8.9 reach end of life?
Oracle PeopleSoft FMS/ESA/SCM 8.9 reached end of life on August 31, 2010. This version is no longer receiving security patches.
Is Oracle PeopleSoft FMS/ESA/SCM 8.9 still supported?
No. Oracle PeopleSoft FMS/ESA/SCM 8.9 reached end of life on August 31, 2010 and is no longer receiving security patches.
What should I upgrade to from Oracle PeopleSoft FMS/ESA/SCM 8.9?
The recommended upgrade from Oracle PeopleSoft FMS/ESA/SCM 8.9 is Oracle PeopleSoft HCM 9.2 (Continuous Innovation) — the latest actively supported version. Check the Oracle PeopleSoft full timeline for all supported versions.
What are the security risks of running Oracle PeopleSoft FMS/ESA/SCM 8.9 past EOL?
When Oracle PeopleSoft FMS/ESA/SCM 8.9 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Oracle PeopleSoft should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →