Live / Nexcess / Incident
Nexcess: PHP Security Vulnerability Assessment (CVE-2026-109618 & CVE-2026-109619)
Nexcess · nexcess.netmonitoring2026-10-29 19:41 UTC
Public — what happened
Summary
Nexcess said it is dealing with two serious PHP security flaws, CVE-2026-109618 and CVE-2026-109619, which it said could let an outsider run code remotely on web servers using PHP 5.4 or later. The company began posting on 2026-10-21 at 16:06 UTC, first testing how to apply fixes safely, and by 2026-10-22 it said it was rolling out patched PHP versions across its hosting systems. Through its latest update on 2026-10-26 at 10:42 UTC, Nexcess said the rollout was going well but was still underway, so the incident is not marked resolved. It told customers how to check their site's PHP version and advised anyone on an unsupported or end-of-life version to move to a supported one.
Timeline
- Started — 2026-10-21 16:06 UTC
- Investigating — 2026-10-21 16:06 UTC (2 updates)
- Identified — 2026-10-22 14:42 UTC (12 updates)
- Monitoring — 2026-10-29 19:41 UTC
- 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 Nexcess 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 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 44, 2026, our weekly internet health report.