Liquid Web Status · History · Incident #5323
ACTIVE INCIDENTJanuscape Vulnerability (CVE-2026-53359)
Minor · Started Jul 9, 2026 · 10:34 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Liquid Web Status · History · Incident #5323
ACTIVE INCIDENTMinor · Started Jul 9, 2026 · 10:34 AM
Duration
Ongoing
Severity
Minor
Detection lead
—
User reports
—
Summary
Our teams are continuing to deploy the required security updates across affected systems in response to the Januscape Vulnerability (CVE-2026-53359). As part of this remediation, some systems require a controlled reboot to complete the patching process. Following each reboot, we are validating system availability, service health, and network connectivity. Systems that do not return to service as expected are being actively investigated and restored by our operations teams. We understand the importance of maintaining availability and are working carefully to complete this remediation while minimizing customer impact. Additional updates will be provided as patching and validation efforts continue.
Started
Jul 9, 2026 · 10:34 AM
Status
Identified
Duration
Ongoing
Severity
None
Event timeline
Investigating
Jul 9 · 10:34 AM Liquid WebOur team is currently assessing the impact and scope of Januscape Vulnerability (CVE-2026-53359), and its impact on servers in our fleet and the best way to apply patches to our hosting infrastructure. We will be sending communications to any affected customers as we work to apply the necessary mitigations. Next Steps: Teams are currently in review of vulnerability; subsequent status updates will follow.
Identified
Jul 13 · 1:49 PM Liquid WebOur teams are continuing to deploy the required security updates across affected systems in response to the Januscape Vulnerability (CVE-2026-53359). As part of this remediation, some systems require a controlled reboot to complete the patching process. Following each reboot, we are validating system availability, service health, and network connectivity. Systems that do not return to service as expected are being actively investigated and restored by our operations teams. We understand the importance of maintaining availability and are working carefully to complete this remediation while minimizing customer impact. Additional updates will be provided as patching and validation efforts continue.
Pattern
WP2Shell Wordpress Core Critical Remote Code Execution Vulnerabilities, CVE-2026-60137 and CVE-2026-63030
Jul 17, 2026
View incident →Power Outage in Phoenix, AZ
Jul 16, 2026 · 4h 23m
View incident →Apache Service Disruption Following ModSecurity Update
Jul 15, 2026
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026