Update status: cPanel lists cPanel & WHM 136.0.37 as an August 27, 2026 Targeted Security Release. If your server is maintained on the 136 line, schedule the vendor-supported update through normal change control and validate the panel, webmail, and hosted-service workflows afterward.
Who should review this release
This checklist is for hosting administrators, resellers, and site owners who manage a server or hosting account on a maintained cPanel & WHM 136 release. It is not a reason to change a release tier, enable unrelated features, or alter a provider-managed maintenance plan. Managed customers should confirm the provider's maintenance timing and support process before taking action.
Plan the maintenance window
- Confirm the installed cPanel & WHM version and the release tier that the server is already approved to use.
- Review the 136 change-log entry and the normal Update Preferences policy so the maintenance owner knows what will change and who will validate it.
- Use the existing recovery contact, restore procedure, and customer-maintenance process. Keep backup retention and customer backup schedules unchanged for this routine panel update.
- Tell affected account owners when panel or webmail access might be briefly interrupted and name the support contact for post-maintenance issues.
Apply the supported cPanel update
Use the normal cPanel & WHM update workflow that is approved for the server. Let the maintenance complete, allow expected service restarts to settle, and record the final installed version in the change record. Do not disable protective controls or broaden access simply to work around an unrelated application issue during the window.
Verify the services people use
- Confirm that administrators can sign in to WHM and that a representative account can use cPanel normally.
- Check webmail access for a representative mailbox and review the mail flow and authentication checks that are part of the usual maintenance validation.
- Open representative hosted sites over HTTPS and confirm that scheduled tasks, DNS-dependent services, and monitoring return to their normal state.
- Review the maintenance record and normal service logs for unexpected errors, then hand exceptions to the responsible hosting or application owner instead of making unplanned configuration changes.
Keep the follow-through useful
For server-wide security maintenance, keep a short record of the source, approved window, final version, validation owner, and any customer follow-up. The WHM Security Advisor and EasyApache checklist can help with the hosting-side review, while WordPress Support covers application checks after server maintenance. If you are planning a later platform transition, review the separate cPanel & WHM 138 rollout checklist rather than combining this targeted maintenance window with a broader interface change.
