Cloudera on Cloud End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cloudera on Cloud versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cloudera-on-cloud)
Cloudera on Cloud lifecycle status — the real story
Cloudera on Cloud — formerly CDP Public Cloud — runs on the 7.2.x line, and it has the nearest deadline of any Cloudera product: 7.2.18 reaches end of support in September 2026. That is the current version for most managed deployments, so this is not a legacy-estate problem; it is a this-quarter problem for teams that have not scheduled the runtime upgrade.
The earlier 7.2.x releases are long gone — 7.2.17 ended June 2025, 7.2.16 ended June 2024, 7.2.15 ended November 2023 — and the cadence tells you what to expect: roughly two years per release, with no LTS designation anywhere in this line. Cloud deployments feel maintenance-free because the infrastructure is managed, which is exactly why the runtime version underneath them tends to go unwatched until the support notice arrives.
Spark runtimes on Cloudera on Cloud follow their own schedule and are worth checking separately: Spark 2.4.8, 3.2.3 and 3.3.x are all deprecated as of September 2026, while Spark 3.5.x follows the Data Lake support policy. Cloudera publishes its lifecycle commitments at month granularity (“EoS September 2026”) rather than as exact days. The dates in this table normalise each published month to its final day, which is how Cloudera’s own support lifecycle policy reads; treat them as the end of the stated month, not as a guaranteed cut-off timestamp.
What does Cloudera on Cloud end of life mean for your organization?
When a version of Cloudera on Cloud 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 Cloudera on Cloud 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 Cloudera on Cloud versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Cloudera on Cloud has 3 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Cloudera on Cloud exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.