cPanel, nginx, Apache and OpenSSL security updates, November 2026
The server-stack sections of the November 2026 weekly briefings in one place: the cPanel & WHM release that fixes a file write as root by an authenticated user, the nginx versions to be on now that an old rewrite bug is circulating again, Apache httpd 2.4.70, and OpenSSL’s five low-severity fixes due on 1 December. 2.4.70 is no longer the Apache release to run: 2.4.71 fixes the critical HTTP/2 flaw CVE-2026-119618, which has an advisory of its own. So do the kernel, PHP and Brotli items from the same weeks, linked at the end.
Prepared by G. Schad, WordPress and Linux security specialist
This page collects the server-stack sections of the weekly briefings of 2, 9 and 16 November 2026, oldest first. Each section is dated; the 9 November Apache section carries a correction pointing to 2.4.71.
cPanel & WHM
Fixed in 11.110.0.154, 11.134.0.67, 11.136.0.51 and 11.138.0.19: root file write, calendar read, Roundcube
nginx
Run 1.30.6 stable or 1.31.8 mainline; CVE-2026-42945 is May’s bug, fixed in 1.30.1
Apache httpd
Run 2.4.71 (11 November): 2.4.55 to 2.4.70 have the critical HTTP/2 flaw CVE-2026-119618
OpenSSL
Five low-severity fixes; 4.1.1, 4.0.4 and 3.5.10 due on 1 December
Confirm
The running version of each service, not the package that is installed
2 November · cPanel & WHM · three fixes
cPanel: an authenticated user could write files as root, and anyone could read calendars
cPanel published two advisories dated 20 October whose CVE records became public on 2 November. CVE-2026-105476 is an improper link resolution flaw, CWE-59, that lets a remote authenticated user write arbitrary root-owned files, which is privilege escalation to root by another name; it is scored 8.8 with a vector that needs only low privileges, and it is credited to a researcher known as Boomerang. The briefing source this issue draws on describes the starting point as a reseller account; the CVE record says authenticated users without qualification. Until cPanel’s text has been read against your own account types, assume any login to the panel is in scope. CVE-2026-105475 is a NUL-byte handling flaw that lets an unauthenticated remote attacker read any mail account’s calendar and contact data, scored 8.7 on CVSS 4.0. Both are fixed in 11.110.0.154, 11.134.0.67, 11.136.0.51 and 11.138.0.19; the 138 change log dates 138.0.19 to 26 October and lists only a security-hardening line for them.
The same 138.0.19 build updates Roundcube to 1.6.20, which Roundcube released on 19 October alongside 1.7.5 with 20 security fixes. The one with the highest reach is CVE-2026-113386, an IMAP command injection: a logged-in webmail user can put a carriage return and line feed into the uid parameter of the headers and view-source actions and have the IMAP server run a command of their choosing on their own mailbox. A sibling, CVE-2026-114720, does the same through the flag parameter of the mark action. Authenticated, scored 7.1, and in a shared-hosting context the authenticated user is any customer or any phished mailbox. Check the Roundcube version a server actually runs rather than the cPanel branch, and on branches other than 138 read the change log for the build that carries 1.6.20.
A phpMyAdmin WebAuthn flaw disclosed this period is reported, in the briefing source, as not affecting the phpMyAdmin that cPanel bundles, on cPanel’s own assessment. This briefing could not find a published cPanel statement to quote, so treat that as unconfirmed, and in any case it says nothing about a phpMyAdmin installed by hand outside the managed package.
Figure 1 · At a glance
The panel, nginx, Apache and OpenSSL: the versions to be running in November.
Question
Answer
cPanel & WHM
Root file write by an authenticated user: 11.110.0.154 · 11.134.0.67 · 11.136.0.51 · 11.138.0.19
nginx
CVE-2026-42945 is May’s bug, fixed in 1.30.1; run 1.30.6 or 1.31.8
Apache httpd
Run 2.4.71: 2.4.55 to 2.4.70 have the critical HTTP/2 flaw CVE-2026-119618
OpenSSL
Five low-severity fixes; 4.1.1, 4.0.4 and 3.5.10 due 1 December
Confirm
The running version of each service, not the installed package
The points that decide what to do about the cPanel, nginx, Apache and OpenSSL updates covered in the November 2026 briefings, as stated in the sections below.
Vulnerability
Who can use it
What it gives
Fixed in
CVE-2026-105476, CVSS 8.8
An authenticated cPanel or WHM user; the CVE vector needs low privileges
Arbitrary file write as root, so full control of the server
9 November · nginx · CVE-2026-42945 and the current releases
nginx: the rewrite bug on social media this week is from May, and the release to run is 1.30.6
CVE-2026-42945 is doing the rounds on X with a fresh Nuclei template, and it is real: a heap buffer overflow in ngx_http_rewrite_module affecting 0.6.27 to 1.30.0, which VulnCheck reported exploited from 16 May, days after the fix. It is not new. nginx.org rates it medium, third parties score it 9.2, and public analyses describe the trigger as a rewrite with an unnamed capture such as $1, a question mark in the replacement, and another rewrite, if or set in the same scope; code execution needs ASLR off, and otherwise the result is a crashed worker. It was fixed in 1.30.1 and 1.31.0 together with CVE-2026-42926, CVE-2026-42946, CVE-2026-42934 and CVE-2026-40460.
Since then nginx.org has published a dozen more advisories, including a second rewrite-module overflow (CVE-2026-9256, fixed in 1.30.2), a major-severity overflow with map and regular expressions (CVE-2026-42533, fixed in 1.30.4) and, on 14 October, five medium fixes in 1.30.6 and 1.31.7: an overflow with alias and rewrite, an overflow in script evaluation, HTTP/3 request body injection, TLS session-ticket forgery and a use-after-free with SSI and AIO. 1.31.8 mainline followed on 21 October. A server that patched to 1.30.1 for this CVE in May is behind; the stable release to run is 1.30.6, or your distribution’s backport of it.
The second command lists rewrites that use a numbered capture and a question mark, which is a quick way to see whether a WordPress configuration has the shape the analyses describe. It is an audit aid, not a test for the vulnerability: the upgrade is the fix either way.
Apache httpd 2.4.70: a maintenance release on top of last month’s twenty CVEs
Apache released httpd 2.4.70 on 6 November and recommends it over all earlier versions. Its condensed changelog has five entries: a heap buffer overflow fixed in mod_dav_lock, where dav_size_indirect() reserved space for the stored key length as an int and wrote it as an apr_size_t; an integer overflow in mod_substitute that the changelog says needs very special setups; mod_cache no longer storing a response whose Vary: * was set by Header always; higher environment, URI and argument limits in mod_cgid; and a fix for the mod_authnz_ldap crashes that 2.4.69 introduced on Windows. At the time of writing, Apache’s vulnerability page lists no CVEs against 2.4.70; the last security fixes are the twenty in 2.4.69 from 1 October.
So the priority depends on where a server is. Below 2.4.69, it is missing twenty CVEs and should move now, to 2.4.70 directly. On 2.4.69, 2.4.70 is a normal update unless the server uses WebDAV locking, mod_substitute or LDAP authentication, in which case it is worth doing this week. On cPanel, check the EasyApache 4 change log for the ea-apache24 build that carries 2.4.70 rather than assuming the next update brings it; on distributions, the version string will often stay at an older number with the fixes backported, so read the package changelog.
OpenSSL: five low-severity fixes, releases on 1 December, nothing to do today
OpenSSL announced five low-severity fixes on 10 November. They are already merged in its public repository, and releases 4.1.1, 4.0.4 and 3.5.10 are scheduled for 1 December. Four of them affect only the 4.1, 4.0 and 3.5 branches. Two are in QUIC: uninitialised stack bytes used during peer detection (CVE-2026-88822), and retransmitted CRYPTO frames causing a denial of service or a one-byte disclosure (CVE-2026-95691). Two are in AES-GCM-SIV: an AAD forgery after a zero-length incremental update (CVE-2026-88823), and an out-of-bounds read with incorrect IV length handling (CVE-2026-95692). The fifth, an infinite loop in CMS_encrypt() with an EC group order of 1 (CVE-2026-107496), reaches back to 3.0, 1.1.1 and 1.0.2. On 4.0 and later it only affects builds with explicit-curve support enabled, and the fixes for the old branches go only to premium-support customers.
For a WordPress server this is a calendar entry, not an incident. None of the five is in ordinary TLS over TCP. The QUIC issues matter only where HTTP/3 or another service runs on OpenSSL’s own QUIC implementation, and FIPS modules are not affected. Plan the distribution updates for when they land after 1 December, and restart the services that link OpenSSL at that point.
Common questions about the November server updates
Who can use the cPanel root file-write flaw?
An authenticated user. The CVE record’s vector requires only low privileges; the briefing source this issue draws on describes a reseller account; cPanel’s advisory could not be read directly at compile time. Treat any panel login as in scope, update to 11.110.0.154, 11.134.0.67, 11.136.0.51 or 11.138.0.19, and review reseller accounts, tokens, SSH keys and recent root-level changes afterwards.
Do I need nginx 1.30.6 if I patched CVE-2026-42945 in May?
Yes. 1.30.1 fixed that bug, and nginx.org has published a dozen more advisories since, including a major-severity overflow fixed in 1.30.4 and five fixes in 1.30.6 on 14 October. Run 1.30.6 stable, 1.31.8 mainline, or your distribution’s backport of them.
Choose the response path
Several servers need these fixes confirmed: choose the response path.
The servers under the sites
Get Apache, HTTP/2 and the rest of the web stack checked on every host.
Best when several servers need the Apache version, the protocols per virtual host and the backported packages verified from the running process, the look-back since 11 November done once, and a written result per host.
Get the finding classified and the site restored to a trusted state.
Best when a file-upload plugin left PHP in uploads, wp-config.php went missing, the tampered Quick Page/Post Redirect build turned up, or an account changed hands, and you want every layer removed in one pass.