Tracker · Server stack · October 2026

cPanel, CloudLinux and web-server security updates, October 2026

The server-stack sections of the four October 2026 weekly briefings in one place, oldest first: three cPanel & WHM fixes from 29 September, the CloudLinux bridge-stp-uaf and PwnEscape kernel flaws, new EasyApache 4 builds and a mass scan for AI coding-tool credentials, Apache httpd 2.4.69, the OpenSSL, nginx and PHP fixes that are easy to apply halfway, and WP Toolkit 6.11.5. PHP2Shell and the later kernel flaws have advisories of their own, linked at the end.

This page collects the server-stack sections of the weekly briefings of 5, 12, 19 and 26 October 2026, oldest first. Each section is dated, and describes the fix status on that date.

5 October
cPanel & WHM: three fixes, one of them root; CloudLinux bridge-stp-uaf, CVE-2026-72389; new EasyApache 4 PHP builds
12 October
Apache httpd 2.4.69 with twenty CVEs; OpenSSL, nginx and PHP fixes
19 October
PwnEscape, CVE-2026-99999, on CloudLinux; EasyApache 4 25.89 and 25.90
26 October
WP Toolkit 6.11.5: an authenticated user could write into another account’s domain

5 October · cPanel and WHM

cPanel and WHM: three fixes from 29 September, one of them root

cPanel shipped a targeted security release on 29 September for three vulnerabilities, covering every supported branch. All three are rated critical, and all three start from a login on the server rather than from the open internet. For two of them cPanel says an unprivileged account holder is enough — exactly the access an attacker has after compromising one WordPress site on a shared server. For the third, the advisory does not say which kind of account can reach it; its CVSS vector rates the privileges required as low.

No exploitation of any of the three had been reported by 5 October. The CVE records were published on 2 October.

Figure 1 · At a glance

Four weeks of server-side fixes, from the panel to the kernel.

QuestionAnswer
5 OctobercPanel & WHM: three fixes, one of them root · CloudLinux CVE-2026-72389
12 OctoberApache httpd 2.4.69: twenty CVEs · OpenSSL, nginx and PHP fixes
19 OctoberPwnEscape, CVE-2026-99999 · EasyApache 4 25.89 and 25.90
26 OctoberWP Toolkit 6.11.5: writes into another account’s domain
Separate advisoriesPHP2Shell; CloudLinux ZDI-CAN-33367 and Fragnesia
The points that decide what to do about the cPanel, CloudLinux and web-server updates covered in the October 2026 briefings, as stated in the sections below.

CVE-2026-93698 · Multilang Adminbin · CVSS 9.9

Insufficient validation lets arbitrary commands run through the Multilang adminbin, and cPanel states the result is code execution as root. The most serious of the three: a low-privileged login on the server becomes control of it.

CVE-2026-93697 · Mass Modify Accounts · CVSS 9.0

Stored cross-site scripting in WHM’s Mass Modify Accounts interface. An unprivileged account holder can plant script that runs in a WHM administrator’s session when they open the page, and take administrative actions as them.

CVE-2026-93029 · Manage SSL Hosts · CVSS 9.0

The same kind of attack through WHM’s Manage SSL Hosts interface: stored script that executes in a WHM administrator’s session.

BranchMinimum fixed version
cPanel & WHM 11011.110.0.148
cPanel & WHM 13411.134.0.61
cPanel & WHM 13611.136.0.45
cPanel & WHM 13811.138.0.11
WP Squared11.138.1.13 — named in the advisories, but not yet in the WP Squared changelog on 5 October

5 October · CloudLinux · CVE-2026-72389

CloudLinux bridge-stp-uaf: from a hosting account to root

CVE-2026-72389, known as bridge-stp-uaf, is a use-after-free in the Linux kernel’s network bridge code, disclosed on 5 August. CloudLinux last updated its status on 1 October. On CloudLinux 7h, 8, and 8 LTS, in CloudLinux’s words, “an ordinary hosting account reaches the flaw as shipped”. On a shared hosting server, an ordinary hosting account is exactly what an attacker gets from a compromised WordPress site — so this is a path from one hacked site to root on the whole server. CloudLinux reports no public working exploit so far.

Fixed kernels, 4.18.0-553.157.1.lve.2 for CloudLinux 7h and 8, have been rolling out to the stable channel since 23 September, and KernelCare livepatches for both are on the main feed, which closes the hole without a reboot. CloudLinux 8 LTS is the awkward one: KernelCare does not cover its kernel line, and its fixed kernel was still in beta on 1 October, so it needs that kernel and a reboot once it is released. On CloudLinux 9 and 10 the vulnerable code is present but not reachable by ordinary accounts by default; livepatches exist for both, and a host that gives containers elevated network rights should be treated as exposed.

  1. 01

    Check the running kernel

    uname -r. On CloudLinux 7h or 8, a kernel older than 4.18.0-553.157.1.lve.2 is vulnerable unless a livepatch covers it.

  2. 02

    Check KernelCare coverage

    shell
    kcarectl --patch-info | grep CVE-2026-72389

    A match means the running kernel is patched in memory. kcarectl --info does not list individual CVEs, so an empty result there proves nothing.

  3. 03

    Patch, or mitigate and plan the reboot

    Apply the fixed kernel or the livepatch where one exists for the branch. On CloudLinux 8 LTS, apply the module mitigation if the host does not use bridging, then install the fixed kernel and reboot once it leaves beta.

5 October · EasyApache 4 · credential scanning

New PHP builds, and a mass scan for AI coding-tool credentials

EasyApache 4 v25.86, published on 30 September, brings PHP to 8.2.34, 8.3.35, 8.4.26, and 8.5.11 — the upstream releases of 24 September. Among the fixes are CVE-2026-91765, a high-severity unbounded recursion in the SOAP extension’s server-side XML handling (CVSS 7.5), and CVE-2026-91768, an IPv6 bypass of PHP-FPM’s listen.allowed_clients: the check compared only the first 12 of 16 address bytes, so an allow-list entry effectively admitted a whole /96 network. Installing the release is the easy part. The part that gets missed is checking that every PHP version the accounts actually use was updated, including the older one kept for a single legacy site.

Imunify360 reported on 30 September a large campaign scanning web servers for the credential files AI coding tools keep in a home directory. The most-requested paths were .codex/auth.json~ (3.7 million requests across more than 56,000 servers), .claude/.credentials.json (1.0 million), .config/claude/credentials.json (900,000), and .anthropic/config.json (548,000). The same scanners asked for the equivalent files of Cursor, Gemini CLI, Windsurf, Aider, Continue, Codeium, and Hugging Face, and for backup copies. Activity spiked from 19 September and peaked on 22 September, when the busiest scanner alone sent 13.5 million requests for these and other sensitive files from more than 35,000 mostly cloud-hosted addresses. Imunify360 now ships WAF rules that block these requests from the start; they had blocked 7.3 million requests on nearly 48,000 servers when the post went up.

These files come within reach of a browser when a developer works directly in a site’s directory, when a home directory doubles as a document root, or when a backup is published by mistake. A token in one of them can give the holder the developer’s access to the tool, and through it to code and connected systems.

12 October · Apache httpd · 2.4.69

Apache httpd 2.4.69: twenty CVEs, none above moderate

Apache httpd 2.4.69 was released on 1 October as “a security, feature and bug fix release”, recommended over all previous versions. It fixes twenty vulnerabilities: five rated moderate and fifteen low, none important or critical. Most affect modules a typical WordPress server does not load, such as mod_dav, mod_vhost_alias, mod_auth_digest, and mod_proxy_uwsgi. The one that matters on many WordPress hosts is in mod_http2, because HTTP/2 is widely enabled.

Among the fifteen low-severity fixes are a limited code-execution issue when internal redirects reach non-CGI files in a CGI directory (CVE-2026-42356, 2.4.60 to 2.4.68), a use-after-free in mod_rewrite through %{LA-U:HTTP:...} (CVE-2026-56154), and response smuggling through mod_proxy_uwsgi (CVE-2026-63718).

Moderate CVEModuleWhat it is
CVE-2026-57941mod_http2Use-after-free and wild write through re-entrancy in a shared session buffer
CVE-2026-42528mod_davShared-lock overflow; a client that can take locks can crash child processes
CVE-2026-93546mod_dav_fsInteger overflow from a PROPPATCH with many XML namespaces; crashes workers and corrupts the property database
CVE-2026-63292mod_vhost_aliasStack overflow from an oversized Host header, with VirtualDocumentRoot and a raised LimitRequestFieldSize
CVE-2026-59685core (Windows only)Out-of-bounds write when rewriting canonical names on case-insensitive file systems

12 October · OpenSSL · nginx · PHP

OpenSSL, nginx, and PHP: fixes from the last two weeks that are easy to apply halfway

OpenSSL released 4.0.3, 3.6.5, 3.5.9, and 3.4.8 on 29 September, fixing fourteen CVEs across the four branches: 4.0.3 carries all fourteen, 3.6.5 and 3.5.9 thirteen, and 3.4.8 twelve. The only high-severity one is CVE-2026-84782: DTLS retransmits handshake messages from a stale buffer offset, which can send heap memory to the peer or crash the process. It matters to DTLS users such as VPN, WebRTC, and VoIP services, not to an ordinary HTTPS web server. A moderate use-after-free in the X.509 extension cache, CVE-2026-84783, affects 4.0 only, and several of the low-severity fixes are in QUIC. OpenSSL 3.1, 3.2, and 3.3 are out of support and were not analysed. The public fix for 3.0, which many server distributions still ship, is available only to premium-support customers as 3.0.23, so on those systems the fix comes from your distribution’s own backport.

nginx 1.31.6 and 1.30.5, released on 15 September, fix CVE-2026-90439, a heap buffer overflow in a worker process when HTTP/3 is used with OpenSSL 3.5.0 or earlier. nginx rates it medium. Only builds that include ngx_http_v3_module are affected, and the module is not built by default; nginx -V shows whether --with-http_v3_module is present. HTTP/3 is served only on listen sockets marked quic. If you cannot upgrade yet, removing quic from the listen directives, together with the Alt-Svc header that advertises it, or setting http3 off, turns it off. The July releases 1.31.3 and 1.30.4 fixed CVE-2026-42533, a major-severity buffer overflow when map is used with regular expressions, which affected every version from 0.9.6.

PHP’s 24 September security releases, 8.2.34, 8.3.35, 8.4.26, and 8.5.11, were covered here last week through cPanel’s EasyApache 4 update. One of their fixes deserves a second look on servers that do not use cPanel. CVE-2026-91767 is a heap over-read in PHP’s OpenSSL wildcard name matching: a malicious TLS server can present a certificate with a crafted wildcard common name and make the PHP client read past a buffer, which can crash it or disclose memory. The PHP advisory rates it moderate, CVSS 6.5. Because verify_peer_name is on by default, ordinary outbound HTTPS calls are exposed: update checks, API requests, webhooks. Debian shipped a fixed php8.4 for trixie on 25 September. Ubuntu’s tracker, last updated 7 October, still listed every supported PHP package as vulnerable, with no update notice.

19 October · CloudLinux · CVE-2026-99999

PwnEscape: a guest-to-host kernel flaw with no fixed CloudLinux kernel yet

CVE-2026-99999, which its finder calls PwnEscape, is a flaw in how the Linux kernel handles checksum metadata from virtio-net. A guest sends a packet with an unfinished checksum and a csum_start value that points inside the IPv4 header; when the host fragments the packet and completes the checksum, two attacker-controlled bytes land in a header the kernel has already validated. The kernel then re-reads the header length and copies that many bytes into each fragment, which leaks host heap memory back to the guest. The bug has existed since Linux 2.6.27. It was found by Paulos Yibelo of pwn.ai during Vercel’s sandbox security challenge, reported privately, and fixed in mainline by Michael Tsirkin of Red Hat; the kernel’s CVE record of 15 October scores it 9.3 and lists fixed stable releases 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113 and 6.18.57.

CloudLinux’s advisory of 16 October is candid about what is and is not known. The researcher reported a host memory leak, a host crash and code execution as root on a test host; CloudLinux has not reproduced the attack, no public proof of concept exists, and it has seen no exploitation. CISA has not added the CVE to its catalog. CloudLinux nonetheless treats every supported kernel as affected: CloudLinux 7, 7h, 8, 8 LTS, 9, 9 LTS, 10 and CloudLinux for Ubuntu 22.04. As of that advisory no fixed kernel had shipped for any of them. CloudLinux 9 and 10 wait on AlmaLinux’s kernel, 8 LTS and 9 LTS on the TuxCare extended-support kernel, and the Ubuntu build follows Canonical’s fix through apt.

The KernelCare livepatch is the only thing that has moved. The patch for the EL9 family is rolling out, and the advisory names K20261016_0002 for AlmaLinux 9 and CloudLinux 9 as being in the main feed, with the RHEL, Oracle and Rocky 9 patches still in testing; el8 and el10 are in progress. The advisory is inconsistent with itself in places, saying both that the EL9 patch is in the test feed and that it is in the main feed, and giving two different verification commands, so check rather than assume: update, then search the patch information for CVE-2026-99999.

shell
kcarectl --update
kcarectl --patch-info | grep CVE-2026-99999

Servers licensed through CLN apply livepatches automatically; servers managed through KernelCare ePortal follow the rules set there.

EnvironmentExposureWhat to do now
KVM host with VMs you do not controlHighest. The guest route needs nothing on the host and does not depend on user namespacesApply the livepatch where it exists. Until a fixed kernel ships, consider disabling checksum offload for untrusted guests (csum=off,guest_csum=off on the virtio-net device, or the csum and guest driver options in libvirt). It needs a guest restart and costs throughput
Shared hosting without VMsOnly where an unprivileged user can create user and network namespaces. CloudLinux 8 and later enable unprivileged user namespaces by defaultCheck sysctl user.max_user_namespaces, or run unshare -Urn as an ordinary user; if it fails, the local route is closed. CloudLinux has not confirmed the local route is exploitable
CloudLinux 9 with KernelCareAs above, with a livepatch availablekcarectl --update, then confirm CVE-2026-99999 appears in kcarectl --patch-info
Every other CloudLinux kernelAs above, nothing shipped yetWatch the advisory for the kernel or livepatch for your stream; reboot when the kernel arrives

19 October · cPanel · EasyApache 4

EasyApache 4 25.89 and 25.90: five ModSecurity evasions, OpenSSL 1.1, Passenger and libcurl

EasyApache 4 25.89, released on 7 October, moves ea-apache24-mod_security2 from 2.9.14 to 2.9.15, the upstream release of 29 September. cPanel lists five CVEs against it. Two matter most to a WordPress host because they are evasions, not crashes: a request can be built that passes the firewall’s rules and still reaches the application with the payload intact. The release also patches ea-openssl11 for the five CVEs in OpenSSL’s 29 September advisory, including the high-severity DTLS flaw CVE-2026-84782 covered here last week, and moves Passenger to 6.2.0, which fixes an unauthenticated Watchdog API and a Watchdog privilege escalation. Note the behaviour change: an empty watchdog_api_server_authorizations value used to skip authentication and now allows none.

EasyApache 4 25.90, released on 14 October, patches ea-libcurl 8.17.0 for six CVEs that cPanel rates low, among them a bearer-token leak on cross-protocol redirects and an HTTP/2 server-push use-after-free, and reworks ea-podman: the Jailshell and CageFS command-line paths now run through admin actions instead of a full-access API token, and host ports reserved by a failed container install are released. Neither release touches Apache itself; the 2.4.69 update with its twenty CVEs was 25.88 on 2 October.

ModSecurity CVEcPanel ratingWhat it is
CVE-2026-104269HighThe multipart parser reads only the plain filename parameter, not RFC 2231 filename*. A harmless filename passes the file-upload rules while a backend that prefers filename* saves the file under a malicious name. Upstream notes PHP reads only filename, so the bypass matters for Go, Python, Node and Java applications behind the same firewall
CVE-2026-104259ModerateremoveComments leaves a comment that directly follows another, so /*A*//*B*/ keeps /*B*/. Inline comments can carry SQL injection or XSS past rules that rely on the transformation
CVE-2026-61812ModeratehtmlEntityDecode knew five named entities; browsers decode 44 more. An entity-encoded colon or equals sign passes 35 OWASP CRS rules and still renders as the plain character
CVE-2026-73857HighUninitialised pointer in the XML request body processor when SecParseXmlIntoArgs is on. Upstream scopes it to libmodsecurity 3.0.15 and later and says version 2 is not affected; cPanel lists it in the 2.9.15 notes regardless
CVE-2026-61813LowRemote rule downloads verified the TLS hostname with libcurl’s weaker setting

26 October · cPanel · WP Toolkit

WP Toolkit 6.11.5: an authenticated user could write files into another account’s domain

cPanel’s article, published on 13 October and updated on 22 October, describes CVE-2026-107663 in WP Toolkit, which ships with cPanel & WHM: in 6.11.4 and earlier, an authenticated user may be able to place malicious files in a domain owned by another user on the same server. The article gives no severity score, and as of 26 October the CVE record has not been published at MITRE or NVD, so the vendor description is all there is. Read in the context of this week, it is the lateral step: a compromised customer account, whether through PHP, a plugin or a stolen key, becomes PHP files in a neighbour’s document root, on a product whose purpose is to manage every WordPress site on the server.

The fixed version is 6.11.5. Because WP Toolkit updates on its own schedule rather than with cPanel & WHM, check the installed version rather than the cPanel version, and update through the installer script cPanel’s article links from wp-toolkit.plesk.com with the version pinned if the server has not already picked it up:

shell
grep version /usr/local/cpanel/3rdparty/wp-toolkit/build.json

On a server that ran 6.11.4 or earlier with more than one customer, add one check to this week’s review: PHP files in any account’s document roots that were created by, or at the times of activity of, a different account’s user. WP Toolkit writes as the target domain’s user, so ownership alone will not show it; creation times against the other account’s session and cron activity will.

Common questions

Common questions about the October server updates

How do I check whether my cPanel server has the 29 September fixes?

Run /usr/local/cpanel/cpanel -V as root and compare the build with the minimum fixed version for its branch: 11.110.0.148, 11.134.0.61, 11.136.0.45, 11.138.0.11, or 11.138.1.13 for WP Squared. If it is behind, /usr/local/cpanel/scripts/upcp --force updates it.

Why would anyone scan web servers for .claude or .codex files?

Because AI coding tools store login tokens in those files, and developers sometimes work directly inside a site’s directory or publish a home directory by mistake. A token found that way can give access to the developer’s account with the tool and to the code and systems connected to it. If such a file was ever reachable over HTTP, rotate the token.

Do I need to restart anything after updating OpenSSL?

Yes. Running services keep the old library in memory until they restart. Restart the web server, PHP-FPM, mail and anything else that uses TLS, or reboot, and check with needrestart or needs-restarting that nothing still uses the old version.

Is PwnEscape a WordPress problem?

Not directly. It is a Linux kernel flaw that lets a virtual machine attack the host it runs on, and possibly lets a local user do the same where unprivileged user namespaces are enabled. It matters to WordPress hosting because a compromised site gives an attacker exactly that kind of local foothold on a shared server. Until a fixed kernel ships, apply the KernelCare livepatch where it exists and check whether user namespaces are enabled.

Do the ModSecurity fixes change anything for a PHP-only server?

Less than the headlines suggest for the multipart flaw: upstream says PHP reads only the plain filename parameter, so that bypass needs a Go, Python, Node or Java backend. The comment and HTML-entity evasions apply to any application behind the firewall, including WordPress. Install the update either way, and check the firewall is still enabled afterwards.

Choose the response path

Several servers need these fixes confirmed: choose the response path.

The server under the sites

Get every PHP branch, the namespace setting and the account boundaries checked and proven.

Best when several servers need the PHP packages verified by changelog, the logs from 17 October read, the CloudLinux mitigation assessed against what customers run, and WP Toolkit’s cross-account risk reviewed, with a written result per host.

One site, one worrying result

Get the finding classified and the site restored to a trusted state.

Best when an UpdraftCentral-connected site shows a plugin or administrator you did not create, a PHP worker wrote something it should not have, or an exploited plugin left an account behind, and you want every layer removed in one pass rather than one at a time.