Published 2 November 2026
cPanel & WHM version 138 is listed by cPanel for an expected end of life in November 2026. That is a reason for server owners to check their installed version and update plan—not a reason to rush an untested upgrade. cPanel says a version becomes unsupported when it is no longer available in any release tier and reaches end of life; unsupported versions do not receive security updates or bug fixes. The precise timing can depend on the release process, so confirm the current status in cPanel’s documentation and WHM before scheduling work.
This distinction matters to hosting customers, too. A website owner on shared hosting usually does not control the server’s cPanel release tier, but an administrator, agency or reseller managing a WHM server may need to plan and coordinate the transition.
What does cPanel’s November 2026 date mean?
In its version table, cPanel lists version 138 as released in July 2026 with an approximate end-of-life date of November 2026. The same table lists version 134 as a Long-Term Support (LTS) release, with an approximate end-of-life date of June 2027. An expected date is a planning signal, not proof that a particular server has stopped receiving updates: check its version and release tier, and verify the current support status against cPanel’s published information.
Release tiers affect when updates arrive. cPanel describes LTS as a version supported for the year, with security and other critical updates during its lifespan. RELEASE and STABLE are other production tiers; EDGE is intended for controlled testing, not production. Servers on RELEASE, STABLE or LTS may have an automatic-upgrade delay of several business days, while the exact behaviour depends on tier and update conditions.
Important: Do not switch release tiers or force a major upgrade just to match a version number. cPanel says a major-version upgrade cannot be downgraded, and recommends checking compatibility and staging the upgrade on a test system first.
Who needs to take action?
- WHM server administrators: Identify the installed cPanel version, release tier, operating system and any update blockers. If version 138 is installed, check cPanel’s current end-of-life status and decide on a supported update path.
- Hosting resellers: Ask the server provider whether the server is scheduled for an update, whether reseller access or custom integrations will be affected, and what customer notice is planned.
- Website owners on shared hosting: You generally cannot update cPanel or WHM yourself. Ask your host if you have a specific compatibility concern; continue maintaining your application, plugins, PHP version and backups separately.
- Agencies and developers: Check custom WHM integrations, deployment scripts, monitoring and any plugins that depend on server interfaces. Test them against the planned environment before production changes.
A practical pre-upgrade checklist
- Record the current state. In WHM, note the displayed cPanel version and release tier. Record the operating system, database version, PHP versions, installed extensions, mail configuration and any custom services. For client sites, list key domains and how they use PHP, databases, cron jobs and outbound email.
- Confirm the supported destination. Review cPanel’s product-version table, deprecation plan and operating-system compatibility information. Do not assume that a supported cPanel version is automatically compatible with every old operating system or third-party plugin.
- Review blockers and dependencies. Check WHM notices and update reports. Review custom integrations with the relevant developers or vendors, particularly if they rely on deprecated APIs, plugins, PHP versions or database software. Do not remove dependencies until you know which accounts use them.
- Prepare recovery options. Confirm that recent account and system backups exist, are accessible, and include the data and configurations needed for recovery. Establish who can restore them and how long restoration may take. A backup is not a rollback plan unless it has a usable restore path.
- Test before production. Where possible, stage the upgrade on a representative test system. Exercise login, websites, control-panel access, DNS, SSL, databases, scheduled jobs, mail sending and receiving, backups, and reseller functions. Pay special attention to custom applications rather than only checking that the WHM page loads.
- Schedule and communicate. Choose a maintenance window appropriate to your business, tell affected clients what to expect, and make sure the responsible administrator can review logs and respond if checks fail.
Verify services after the update
After an upgrade, test representative sites from outside the server and from a normal browser. Check that pages load over HTTPS, login and checkout flows work, forms send mail, and scheduled tasks run. For hosted email, test both inbound and outbound messages. Review server and application logs for new errors, then confirm monitoring and backup jobs still run. A control-panel version change alone does not demonstrate that every hosted service is healthy.
cPanel documents WHM’s “Upgrade to Latest Version” interface for updates, and the command-line updater for administrators who manage updates as root. Follow the instructions for your system and release tier; avoid copying commands from unrelated servers or making manual package changes without understanding their effects.
What shared-hosting customers and resellers should ask
HostCupid Web Solutions Private Limited is a Chennai-based hosting and website-services company operating since 2018, with shared, WordPress, reseller and master reseller hosting among its services. For a HostCupid customer who depends on cPanel access—or a reseller who manages client accounts—the useful next step is to ask the provider whether a server-side update is planned and whether any specific account action is needed. The customer use case is coordination: the host manages server-level changes, while site owners help identify application dependencies and test their own critical workflows.
For independent server administrators, cPanel’s version schedule is a prompt to verify facts and prepare, not a substitute for change control. Confirm the installed build, supported operating system, release tier and current vendor guidance; test the path; keep recovery options ready; and verify real services afterwards. That measured process helps protect client websites without turning an expected end-of-life date into an avoidable outage.
Sources
- Product Versions and the Release Process — cPanel & WHM Documentation · 2026-10-02
- 138 Change Log — cPanel & WHM Documentation · 2026-10-26
- Update Preferences — cPanel & WHM Documentation · 2026-08-25
- How to Update Your System — cPanel & WHM Documentation · 2026-07-08
