|
Vulnerability Type |
Remote code execution and denial of service in the bundled Apache HTTP Server: CVE-2026-119618, CVE-2026-106023, CVE-2026-109163 |
|
Severity factors |
Apache rates CVE-2026-119618 Critical. A server is exposed to it only when Apache loads mod_http2 and clients can negotiate HTTP/2 with Apache. FileCloud's Windows and Ubuntu builds do not load mod_http2; on RHEL it can be loaded, so RHEL servers should be checked. The other two vulnerabilities, rated Important and Low by Apache, apply only to modules that FileCloud does not use. |
|
Versions affected |
All FileCloud Server versions up to and including 23.263.3, on Windows and Linux. |
|
Version fixed |
To be released (FileCloud 23.264, due December 2026) |
Description
On 11 November 2026, the Apache Software Foundation released Apache HTTP Server (httpd) 2.4.71, which fixes three vulnerabilities. Each one is in a single Apache module and applies only when Apache loads that module.
-
CVE-2026-119618 (Critical), mod_http2: a race condition in assign_headers() corrupts the heap and can lead to remote code execution. It affects httpd 2.4.55 to 2.4.70 when mod_http2 is loaded and HTTP/2 is negotiated. FileCloud's Windows and Ubuntu builds do not load mod_http2. On RHEL it can be loaded, so check RHEL servers with the steps below.
-
CVE-2026-106023 (Important), mod_md: a NULL pointer dereference during request processing crashes the child process. It affects httpd 2.4.30 to 2.4.70 when mod_md is loaded. FileCloud does not use mod_md.
-
CVE-2026-109163 (Low), mod_vhost_alias: a 1-byte stack buffer overwrite, following on from CVE-2026-63292. It affects httpd 2.4.69 to 2.4.70 only when VirtualDocumentRoot is configured. FileCloud does not use it.
FileCloud Server 23.263.0 to 23.263.2 bundle httpd 2.4.68, and 23.263.3 bundles httpd 2.4.69. Upgrading from a release older than 23.263.3 also brings in the 20 fixes from httpd 2.4.69 (5 moderate, 15 low). One of the moderate fixes, CVE-2026-59685, is an out-of-bounds write in path handling that affects Windows servers on httpd 2.4.68 and earlier.
A server behind a load balancer or reverse proxy that talks HTTP/1.1 to Apache is not reachable over HTTP/2, even on RHEL.
Interim mitigation
Until you can upgrade, turn off each affected module that your server loads. Apache has not published official workarounds; these steps work because each vulnerability is in a single module. FileCloud does not use mod_md or mod_vhost_alias, and the FileCloud web UI and clients keep working over HTTP/1.1 without mod_http2.
Windows
-
Open a command prompt in
C:\xampp\apache\bin, then list the affected modules that are loaded:httpd.exe -M | findstr "http2_module md_module vhost_alias_module"A module that is not listed is not loaded, and its vulnerability does not apply.
-
If md_module or vhost_alias_module is listed, back up
C:\xampp\apache\conf\httpd.conf, then comment out each listed module by adding#at the start of its line:#LoadModule md_module modules/mod_md.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so -
Check the configuration. It should print
Syntax OK. If it reports an unknown command, such as MDomain or VirtualDocumentRoot, the server uses that module: restore the backup and plan the upgrade instead.httpd.exe -t -
Open the FileCloud control panel, and restart the web server.
-
Run Step 1 again to confirm that the modules are no longer listed.
Note: FileCloud's Windows build does not load mod_http2, so CVE-2026-119618 does not apply to Windows servers unless mod_http2 has been added to the configuration.
Linux
Run these commands as root. The checks only read the configuration and are safe on a live server. Each file that the commands change keeps a .bak copy, which Apache does not load.
-
Check the Apache version:
# Ubuntu apache2 -v # RHEL httpd -v -
List the affected modules that are loaded:
# Ubuntu apache2ctl -M | grep -wE 'http2_module|md_module|vhost_alias_module' # RHEL httpd -M | grep -wE 'http2_module|md_module|vhost_alias_module'A module that is not listed is not loaded, and its vulnerability does not apply. Keep the
-woption: without it, md_module also matches systemd_module, which is unrelated. -
On RHEL, if http2_module is listed, offer HTTP/1.1 only and stop loading mod_http2:
# Show where HTTP/2 is enabled and which file loads mod_http2 grep -rnE --include='*.conf' '^\s*(Protocols|LoadModule\s+http2_module|H2)' /etc/httpd/ # Offer HTTP/1.1 only, in every Protocols line grep -rlE --include='*.conf' '^\s*Protocols\b' /etc/httpd/ | xargs -r sed -i.bak -E 's|^(\s*Protocols\s+).*|\1http/1.1|' # Comment out the LoadModule line for mod_http2 grep -rlE --include='*.conf' '^\s*LoadModule\s+http2_module' /etc/httpd/ | xargs -r sed -i.bak -E 's|^(\s*LoadModule\s+http2_module)|# \1|'
-
If md_module or vhost_alias_module is listed, confirm that nothing on the server uses them, then stop loading them:
# Confirm nothing uses them (should print nothing) # Ubuntu grep -rnE --include='*.conf' '^\s*(<?MD[A-Za-z]+|VirtualDocumentRoot|VirtualScriptAlias)' /etc/apache2/ # RHEL grep -rnE --include='*.conf' '^\s*(<?MD[A-Za-z]+|VirtualDocumentRoot|VirtualScriptAlias)' /etc/httpd/ # Stop loading them # Ubuntu a2dismod md vhost_alias # RHEL grep -rlE --include='*.conf' '^\s*LoadModule\s+(md_module|vhost_alias_module)' /etc/httpd/ | xargs -r sed -i.bak -E 's/^(\s*LoadModule\s+(md_module|vhost_alias_module))/# \1/'If the first command prints any lines, the server uses that module: keep it loaded and plan the upgrade to 23.264 instead.
-
Check the configuration, then restart the web server:
# Ubuntu apache2ctl -t && systemctl restart apache2 # RHEL apachectl -t && systemctl restart httpdApache keeps serving on its current configuration until it restarts, so a failed check never takes the server down. On RHEL, if the check reports an unknown H2 directive, comment that line out as well and run it again; step 3 lists any such lines.
-
Run step 2 again: the modules you turned off are no longer listed. On RHEL, also confirm that HTTP/2 is no longer negotiated; this command prints 1.1:
curl -sk --http2 -o /dev/null -w '%{http_version}\n' https://localhost/If a load balancer sits in front of Apache, run this check on the server itself, because the load balancer may answer HTTP/2 on Apache's behalf.
Note: To undo the changes on RHEL, copy each .bak file back over its original and restart the web server. On Ubuntu, run a2enmod md vhost_alias and restart the web server.
Deployment notes for interim mitigation
Multitenant deployments: All tenants share the same installation, so the steps only need to be applied once.
High availability deployments: Apply the steps on every FileCloud web/app node. To avoid downtime, update and restart one node at a time.
FileCloud Online: No action is required. FileCloud Online is not affected, because it does not use the affected functionality in mod_http2, mod_md or mod_vhost_alias.
Fix
-
FileCloud Server up to and including 23.263.3: We recommend upgrading to 23.264 when it is released (due December 2026). It bundles Apache httpd 2.4.71 on Windows, RHEL and Ubuntu. If you turned off HTTP/2 as an interim step, you can leave it off.
-
FileCloud Online: No action is required.
If you have any questions about this advisory, please contact FileCloud support.