Live / Mews / Incident
Mews: Critical 0 day PHP vulnerability
Mews · mews.comResolved2026-10-21 22:33 UTC
Public — what happened
Summary
Mews said it was aware of a newly disclosed critical security flaw in PHP, a widely used programming language, and began investigating on 2026-10-21 at 12:34 UTC. The company said it was checking its systems for exposure, had added extra monitoring and protective measures, and was following guidance from the PHP maintainers. It reported that fixes had been released by the maintainers and that it was testing and preparing to apply them, and that it had found no evidence that customer data or Mews services were affected. Customers were told they did not need to take any action, and the incident was marked resolved at 22:33 UTC the same day.
Timeline
- Started — 2026-10-21 12:34 UTC
- Investigating — 2026-10-21 12:34 UTC (3 updates)
- Resolved — 2026-10-21 22:33 UTC · 9h 59m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Mews 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 Mews: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Mews report →
More from Mews
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.