Live  /  Nexcess  /  Incident

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

Nexcess · nexcess.netMajor incidentidentified2026-11-13 14:53 UTC
Public — what happened

Summary

Nexcess said it learned on 2026-11-12 at 10:22 UTC of a newly disclosed serious security flaw, CVE-2026-119618, in the HTTP/2 part of Apache HTTP Server, which it said could potentially let an outsider run code remotely through specially crafted requests. The company said it would patch its hosting servers, which requires restarting Apache and causes a few seconds of downtime. Later that day it reported that its engineers had applied the updates to the affected Cloudhosts, with a small number of servers needing individual attention. As of its latest update on 2026-11-13 at 14:53 UTC, Nexcess said it was still rolling out patches across its fleet and the incident was not marked resolved.

Affected

us-midwest-1, us-west-1, uk-south-2, nl-west-1, au-south-1, us-midwest-2

As listed on Nexcess’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 Nexcess 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 Nexcess: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Nexcess report →

More from Nexcess

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

The full archive is on the Nexcess status & history page.

Related: Nexcess status & history. SquidGrid is not affiliated with Nexcess.