# cPanel CVE-2026-41940: check your version, ask your host

> cPanel and WHM CVE-2026-41940 is an exploited login bypass fixed in April 2026. See the fixed builds, how to read your version, and the exact question to send your host.

Canonical: https://red.run.cloud/learn/cpanel-whm-cve-2026-41940-ask-your-host · By Timothy Lindblom · Published 2026-11-04 · Updated 2026-11-04

cPanel and WHM CVE-2026-41940 is a login bypass that let outsiders reach the hosting control panel without a password. It was fixed on 28 April 2026 and is in the CISA exploited list. If you run the server, update to the fixed build for your branch. If a host runs it for you, ask which build your server runs and when it was installed.

| Fact | Detail | Source |
|---|---|---|
| CVE | CVE-2026-41940, missing authentication for a critical function (CWE-306) | [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-41940) |
| Severity | CVSS v3.1 9.8, CVSS v4 9.3 | NVD |
| Affected | cPanel & WHM from 11.40 up to the fixed build on each branch, and WP Squared before 11.136.1.7 | [VulnCheck](https://www.vulncheck.com/advisories/cpanel-and-whm-authentication-bypass-via-login-flow) |
| Fixed | 28 April 2026, build 136.0.5 and matching builds on older branches | [cPanel change log](https://docs.cpanel.net/changelogs/136-change-log/) |
| Exploitation | CISA catalog entry added 30 April 2026, ransomware use marked Known | [CISA](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41940) |
| Checked | 4 November 2026 | this page |

This page is about who must act, what to read on your own panel, and what to put in writing. For the PHP bug that hit the same servers in October, see [what to ask your provider about PHP2Shell](/learn/php2shell-shared-hosting-what-to-ask-your-provider) and [updating PHP in cPanel](/learn/php2shell-cpanel-update-php). The two are separate problems.

## Who is affected, and who has to fix it?

Anyone whose site sits on a server running cPanel and WHM, at a build below the fixed one for its branch. The people who can change that are the ones with root on the server.

| Your hosting | Who updates cPanel and WHM | What you do |
|---|---|---|
| Shared or reseller hosting with cPanel | Your host | Ask for the build number and install date. You cannot patch it |
| Managed VPS or dedicated, host runs the panel | Your host, by contract | Ask the same question and ask where it is written in your plan |
| Unmanaged VPS or dedicated with cPanel | You | Update to the newest build on your tier, then review sessions |
| WP Squared | You or your host, by plan | Confirm 11.136.1.7 or later |

Updating WordPress, plugins or PHP on your site does not change the panel. The panel is a separate program that listens on its own login ports. Who owns the patch is also the subject of [how patch ownership splits between you and your host](/learn/who-is-responsible-for-patching-my-website). If your host runs Plesk or aaPanel instead, [the Plesk API import flaw](/learn/plesk-cve-2026-68492-api-site-import-rce) and [aaPanel's 2026 CVEs](/learn/aapanel-bt-panel-2026-cves) have their own fixes, and [the other hosting panel guides](/learn/topics/hosting-panels) cover the rest.

## What happened, in dates?

| Date | Event | Source |
|---|---|---|
| 28 April 2026 | cPanel ships 136.0.5 with a security fix to session loading and saving | [cPanel change log](https://docs.cpanel.net/changelogs/136-change-log/) |
| 29 April 2026 | NVD publishes the record. The Canadian Centre issues AL26-008 | [Canadian Centre](https://www.cyber.gc.ca/en/alerts-advisories/al26-008-vulnerability-affecting-cpanel-webhost-manager-whm-cve-2026-41940) |
| 30 April 2026 | CISA adds it to the catalog, due date 3 May 2026 | CISA |
| 30 September 2026 | NVD record last modified | NVD |

The CISA record is first-party for the exploited status and the ransomware flag. We found no primary source for when exploitation began, so we give no date for it. [watchTowr Labs](https://labs.watchtowr.com/the-internet-is-falling-down-falling-down-falling-down-cpanel-whm-authentication-bypass-cve-2026-41940/) and NVD both note that public exploit code exists. We do not link it.

## Which cPanel version is the fixed one?

Fixed builds are floors. The cPanel change log for the 136 branch runs to 136.0.51 (26 October 2026) at our 4 November check, so a server at or above the listed number on its own branch has the fix.

| Branch | First fixed build | Source |
|---|---|---|
| 86 | 11.86.0.41 | Canadian Centre |
| 110 | 11.110.0.97 | Canadian Centre |
| 118 | 11.118.0.63 | Canadian Centre |
| 94 | 11.94.0.28 | NVD only |
| 102 | 11.102.0.39 | NVD only |
| 124 | 11.124.0.35 | NVD only |
| 126 | 11.126.0.54 | Canadian Centre |
| 130 | 11.130.0.19 | Canadian Centre |
| 132 | 11.132.0.29 | Canadian Centre |
| 134 | 11.134.0.20 | Canadian Centre |
| 136 | 11.136.0.5 | Canadian Centre, cPanel change log |
| WP Squared | 11.136.1.7 | Canadian Centre, NVD |

Table facts checked 24 October 2026. Two sources, two styles: the advisory writes 11.136.0.5, the change log writes 136.0.5. They are the same build. The 94, 102 and 124 branches appear in NVD's affected ranges but not in the Canadian Centre list, so confirm them with cPanel if your server runs one.

Branches released after the fix, such as 138 (cPanel lists its release as July 2026), do not appear in any NVD affected range at our check. A branch with no listed fix is a different case. cPanel's own [release documentation](https://docs.cpanel.net/knowledge-base/cpanel-product/product-versions-and-the-release-process/) says unsupported versions do not receive security updates or bug fixes, so the answer there is a move to a supported branch, not a wait.

## Why is a change log not enough proof?

The fix line in the cPanel change log reads "Fix an issue with session loading and saving". It does not name the CVE. With PHP packages you can search a changelog for a CVE id. Here you cannot, so the number is the evidence. Ask for the build and compare it with the table.

The second trap is the gap between a fix existing and a fix running on your server. cPanel's [upcp documentation](https://docs.cpanel.net/whm/scripts/the-upcp-script/) says security updates run through an hourly job that can be disabled in WHM. A server with that job off, or with updates paused, can sit on an old build for months while the host's support desk says "we update regularly".

<figure class="ln-figure">
<svg viewBox="0 0 720 200" role="img" xmlns="http://www.w3.org/2000/svg" font-family="Geist, sans-serif">
<title>Three things to get in writing from a host: the build, the install date, the review</title>
<rect x="10" y="40" width="200" height="110" rx="14" fill="#FFF1EF" stroke="#EAD3CF"/>
<rect x="260" y="40" width="200" height="110" rx="14" fill="#FFF1EF" stroke="#EAD3CF"/>
<rect x="510" y="40" width="200" height="110" rx="14" fill="#FFF1EF" stroke="#EAD3CF"/>
<text x="110" y="78" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">1. Build number</text>
<text x="110" y="104" text-anchor="middle" font-size="13" fill="#655553">at or above the fixed</text>
<text x="110" y="124" text-anchor="middle" font-size="13" fill="#655553">build for its branch</text>
<text x="360" y="78" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">2. Install date</text>
<text x="360" y="104" text-anchor="middle" font-size="13" fill="#655553">on or before 28 April</text>
<text x="360" y="124" text-anchor="middle" font-size="13" fill="#655553">or a stated later date</text>
<text x="610" y="78" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">3. Look-back</text>
<text x="610" y="104" text-anchor="middle" font-size="13" fill="#655553">sessions and accounts</text>
<text x="610" y="124" text-anchor="middle" font-size="13" fill="#655553">reviewed before the fix</text>
<path d="M214 95 H256 M464 95 H506" stroke="#C70500" stroke-width="3" fill="none"/>
<path d="M250 88 L258 95 L250 102 M500 88 L508 95 L500 102" stroke="#C70500" stroke-width="3" fill="none"/>
<text x="360" y="184" text-anchor="middle" font-size="13" fill="#B00500">Steps 1 and 2 show the patch. Only step 3 speaks to compromise.</text>
</svg>
<figcaption>What to hold before you accept "we patched": the build, the date it went on, and a look-back for the period before the fix.</figcaption>
</figure>

## How do I read my cPanel version?

On shared hosting, log in to cPanel and open Server Information. cPanel's [documentation](https://docs.cpanel.net/cpanel/the-cpanel-interface/server-information-for-cpanel/) says its cPanel Version row is the version of cPanel and WHM running on the server behind your account. The [version page](https://docs.cpanel.net/knowledge-base/cpanel-product/what-is-my-version-number/) adds that the number also appears near the lower left corner of the interface, in cPanel and in WHM.

Write down the full number, for example 11.130.0.19, with the date you read it. Then compare it with the table. If your host has hidden the Server Information page, that is a reason to ask, not a result.

## What do I ask my host?

Send this, by email or ticket, so the answer is written down.

> For the server that hosts [domain]: which cPanel and WHM build is it running today, and on what date was that build installed? Was it updated for CVE-2026-41940 on or before 28 April 2026? If not, on what date? Please also tell me whether you reviewed login sessions and accounts on this server for the period before the update, and whether you changed any credentials.

- [ ] I have the full build number, not just "up to date".
- [ ] The build is at or above the fixed number for its branch.
- [ ] I have an install date, and it is in writing.
- [ ] I asked whether sessions and accounts were reviewed.
- [ ] I saved the reply with its date for clients or auditors.

A reply of "fully patched" or "no action needed" with no build number is an unknown. The same rule appears in how we treat hosts for PHP: a status page, a version selector or a silence does not count as an answer.

## Am I affected? Where you stand right now

<div class="ln-selftest">
<h3>Am I affected? Where you stand right now</h3>
<p>A check from outside your website cannot read the cPanel build, because the panel runs on its own login port on the server. Only you or your host can read it.</p>
<ol>
<li><span class="ln-state ln-state-detected">Detected</span> <strong>The cPanel version you can read is below the first fixed build for its branch.</strong> Treat the server as exposed. Ask the host to update today, or run the update yourself, then start the look-back.</li>
<li><span class="ln-state ln-state-unknown">Unknown</span> <strong>You cannot see a build number, or the host will not give one.</strong> This is the common case on shared hosting. Send the question above and wait for a number, not a reassurance.</li>
<li><span class="ln-state ln-state-confirmed">Confirmed by owner evidence</span> <strong>You hold a build at or above the fixed one, with an install date in writing.</strong> The patch is in place. Whether anyone used the flaw before then is a separate question.</li>
</ol>
<p>No scan, ours included, moves you from "unknown" to "confirmed".</p>
</div>

## How do I update if I run the server?

You need root. cPanel's [Upgrade to Latest Version](https://docs.cpanel.net/whm/cpanel/upgrade-to-latest-version/) page says the feature updates your server to the most recent build available on its release tier, and that it can re-enable automatic updates if they are off. On the command line the [upcp script](https://docs.cpanel.net/whm/scripts/the-upcp-script/) does the same, and `--security` applies critical security updates when available.

```
/usr/local/cpanel/scripts/upcp
```

After it finishes, read the version in WHM again and record it. If the tier you are on has no build at or above the fixed number, move to a tier that does. Until then, [watchTowr](https://labs.watchtowr.com/the-internet-is-falling-down-falling-down-falling-down-cpanel-whm-authentication-bypass-cve-2026-41940/) and the Canadian Centre both advise limiting the admin ports, including WHM's 2087, to trusted addresses at the firewall. That reduces who can reach the login. It does not replace the update.

## Was anything exploited on my server?

CISA lists the flaw as exploited and marks ransomware use as known, and it added the entry two days after the fix. A server patched in May may have been reachable for weeks before. Updating closes the door. It does not remove an account, session or scheduled job someone created while it was open.

If your server ran an unpatched build with the panel reachable from the internet, review these, working from the vendor and researcher guidance:

- Login and access logs for successful panel sessions that have no matching normal login.
- Session files under `/var/cpanel/sessions/`, which watchTowr says can hold entries that do not belong in a session.
- New or changed accounts, reseller users, API tokens, SSH keys and scheduled jobs.
- Files and databases for unexpected changes or encrypted files.

If you find a sign, follow the [step-by-step cleanup after a hack](/learn/website-incident-response-playbook) and [rotate secrets](/learn/rotate-secrets-after-a-breach-guide) from a clean machine. Do not assume a restore fixes it: [a restored backup can still be hacked](/learn/restored-backup-still-hacked-clean-restore-point) if the copy predates the fix. The panel can read what the hosted sites hold, including database passwords and API keys. If you cannot review the server yourself, the question to the host in the previous section is how you find out whether they did.

## What can Red tell me?

The free scan reads the stack your site serves and matches each version to known vulnerabilities. It also looks for panels, consoles and debug pages left online. It is a lookup. It can say a version is affected. It cannot see the cPanel build on the server behind your domain, so it will not confirm this fix. The reasons are laid out in [why outside scans miss server-side versions](/learn/what-an-external-website-scan-cant-prove).

The full scan is $100 per scan. An AI red team lists what it can reach from outside, links findings into one path, proves access once with evidence, and stops. It does not touch the panel's build state either. Neither product replaces the host's written answer.

## Questions people ask

### Is my host patched for cPanel CVE-2026-41940?

We cannot tell you from outside, and we did not find a host that states it for this CVE in our check on 24 October 2026. The fix shipped on 28 April 2026, so most active hosts have had months. Ask your host for the cPanel build number on your server and the date it was installed.

### How do I check my cPanel version on shared hosting?

Log in to cPanel and open Server Information. The cPanel Version row shows the build of cPanel and WHM on the server behind your account. The same number sits near the lower left corner of the cPanel interface. Compare it with the fixed build for its branch in the table above.

### Which cPanel version fixes CVE-2026-41940?

It depends on the branch. For example 11.136.0.5, 11.134.0.20, 11.132.0.29 and 11.126.0.54 are the first fixed builds on their branches. Any build at or above the fixed number on the same branch is fixed. A build on a branch with no listed fix needs a move to a listed branch.

### Was my site hacked through cPanel?

A patched server can still hold an access path planted before the update. CISA lists the flaw as exploited and records ransomware use. Ask your host whether they reviewed sessions and accounts on your server, and change your cPanel and hosting passwords if you cannot get an answer.

### I run my own VPS with cPanel. How do I update?

As root, run the upcp script, or use Upgrade to Latest Version in WHM. Both move the server to the newest build on its release tier. Afterwards read the version in WHM and check that automatic updates are still switched on.

### Can a website scan tell me if my cPanel is fixed?

No. A scan reads what your site serves and matches versions to known records. The cPanel build runs on a login port and on the server, and the scan cannot read it from your website. Only the host or the server owner can show the build and the install date.


## Sources

1. [cPanel & WHM Security Update 04/28/2026 (cPanel support)](https://support.cpanel.net/hc/en-us/articles/40073787579671-cPanel-WHM-Security-Update-04-28-2026): The vendor advisory, linked from NVD and the CISA entry. It returned HTTP 403 to our scripted fetch on 24 October 2026, so the facts below come from the changelog, NVD and CISA records that cite it.
2. [cPanel & WHM 136 change log (docs.cpanel.net)](https://docs.cpanel.net/changelogs/136-change-log/): Build 136.0.5, dated 2026-04-28, lists CPANEL-52908 as a security fix to session loading and saving. Newest build 136.0.51, dated 2026-10-26, at our 4 November 2026 check.
3. [NVD: CVE-2026-41940](https://nvd.nist.gov/vuln/detail/CVE-2026-41940): CVSS v3.1 9.8, CVSS v4 9.3, CWE-306, affected ranges per branch. Published 2026-04-29, last modified 2026-09-30. Read 24 October 2026.
4. [CISA Known Exploited Vulnerabilities catalog entry for CVE-2026-41940](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41940): Added 2026-04-30, due date 2026-05-03, ransomware campaign use marked Known. Read from the catalog feed on 4 November 2026.
5. [Canadian Centre for Cyber Security AL26-008](https://www.cyber.gc.ca/en/alerts-advisories/al26-008-vulnerability-affecting-cpanel-webhost-manager-whm-cve-2026-41940): Released 2026-04-29. Lists the fixed build per branch and recommends restricting admin interfaces.
6. [watchTowr Labs: cPanel & WHM authentication bypass (CVE-2026-41940)](https://labs.watchtowr.com/the-internet-is-falling-down-falling-down-falling-down-cpanel-whm-authentication-bypass-cve-2026-41940/): Researcher analysis: affected port, session directories to review, interim network restriction. Vendor-independent. We link no exploit code.
7. [VulnCheck advisory: cPanel and WHM authentication bypass via login flow](https://www.vulncheck.com/advisories/cpanel-and-whm-authentication-bypass-via-login-flow): Affected range 11.40.0.0 through 11.136.0.4 and WP Squared before 11.136.1.7.
8. [cPanel docs: product versions and the release process](https://docs.cpanel.net/knowledge-base/cpanel-product/product-versions-and-the-release-process/): Release tiers, and the statement that unsupported versions do not receive security updates.
9. [cPanel docs: what is my version number](https://docs.cpanel.net/knowledge-base/cpanel-product/what-is-my-version-number/): The version sits near the lower left corner of WHM and cPanel.
10. [cPanel docs: Server Information for cPanel](https://docs.cpanel.net/cpanel/the-cpanel-interface/server-information-for-cpanel/): Shows the cPanel version of the server behind your account.
11. [cPanel docs: the upcp script](https://docs.cpanel.net/whm/scripts/the-upcp-script/): Command line update, the --security and --force options.
12. [cPanel docs: Upgrade to Latest Version](https://docs.cpanel.net/whm/cpanel/upgrade-to-latest-version/): Updates to the newest build on the server's release tier.
