Live  /  Liquid Web  /  Incident

Liquid Web: Security Advisory: Apache HTTP/2 Vulnerability (CVE-2026-119618)

Liquid Web · liquidweb.comidentified2026-11-13 14:55 UTC
Public — what happened

Summary

Liquid Web said it became aware on 2026-11-12 of a critical security flaw, CVE-2026-119618, in the HTTP/2 component of Apache HTTP Server, which it said could in some conditions let an attacker run code remotely. The company said it planned to update its hosting servers, which would mean Apache restarts causing a few seconds of downtime. Later that day it said a security update was available and that its engineers were testing it before rolling it out to Managed Hosting servers. By 2026-11-13 at 14:55 UTC it said the rollout across its servers was under way, and the issue was not yet marked resolved.

Affected

Cloud Dedicated, Cloud VPS Hosting, CPanel, InterWorx, Plesk

As listed on Liquid Web’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Liquid Web against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Liquid Web: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Liquid Web report →

More from Liquid Web

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Liquid Web status & history page.

Related: Liquid Web status & history. SquidGrid is not affiliated with Liquid Web.