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
Timeline
- Started — 2026-11-12 10:20 UTC
- Investigating — 2026-11-12 10:20 UTC
- Identified — 2026-11-12 21:49 UTC (2 updates)
- Ongoing at last check.
With SquidGrid — where it starts on the route
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 seeCustomers 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.