Apache CVE-2026-119618

Scheduled Maintenance Report for InterServer

Completed

The scheduled maintenance has been completed.
Posted Nov 15, 2026 - 20:55 EST

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Nov 12, 2026 - 20:55 EST

Scheduled

**Incident Name:** Security Advisory: Apache Vulnerability (CVE-2026-119618)

**Current Status:** Monitoring / Customer Action Required

**InterServer Shared Hosting Update:**
We have audited our shared hosting infrastructure against the newly disclosed Apache Remote Code Execution vulnerability (CVE-2026-119618). InterServer shared hosting environments primarily run LiteSpeed web servers, which are completely unaffected by this issue. The small number of shared systems running Apache have already been patched and secured by our engineering team. No action is required for shared hosting customers.

**Action Required for VPS and Dedicated Server Customers:**
If you manage your own VPS or Dedicated Server running Apache, you need to apply this critical security update immediately. Control panel vendors and operating system repositories have released patches to secure the `mod_http2` module (typically bringing Apache to version 2.4.71).

Please log into your server via SSH as theuser and run the applicable commands below to update your system.

### cPanel (EasyApache 4)
cPanel has pushed the fix to the EasyApache 4 repository. Clean your package manager cache, update the packages, and restart the web server: using yum/dnf

```bash
yum clean all
yum update ea-apache24
/scripts/restartsrv_httpd
```

### DirectAdmin
DirectAdmin uses CustomBuild to manage and compile software from source. Navigate to the CustomBuild directory, update the versions script, and recompile Apache:

```bash
cd /usr/local/directadmin/custombuild
./build update
./build apache
```

### Plesk & Standalone Servers (No Control Panel)
Plesk relies entirely on your operating system's default package manager. Even if Plesk is configured to use Nginx as the primary frontend proxy, Apache is still running in the background and must be patched.

Update the module using your OS package manager:

**For RHEL / AlmaLinux / CloudLinux / CentOS:**
```bash
dnf clean metadata
dnf update mod_http2
systemctl restart httpd
```

**For Ubuntu / Debian:**
```bash
apt-get update
apt-get install apache2
systemctl restart apache2
```

**Verification & Mitigation:**
After applying the updates, verify your Apache version by running `httpd -v` or `apachectl -v` to ensure it reflects version 2.4.71 (or that your specific OS package changelog lists CVE-2026-119618). If your operating system vendor has not yet released the patched package to their repository, you can temporarily mitigate the vulnerability by disabling HTTP/2 in your web server configuration.
Posted Nov 12, 2026 - 20:52 EST