Live  /  Kaseya  /  Incident

Kaseya: PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619): Kaseya status - Investigation and Remediation

Kaseya · datto.comidentified2026-10-23 20:20 UTC
Public — what happened

Summary

Kaseya said two critical security flaws were disclosed in third-party PHP software components, which could let an unauthenticated attacker run code remotely, and its security teams began assessing its products starting 2026-10-21 at 21:51 UTC. On 2026-10-23 Kaseya said it had finished reviewing its product line: many products are fully patched, many are unaffected, and several Datto products have temporary protective measures in place while fixes are developed. It also said Unitrends customers need to take an extra step described in its knowledge base. The incident is not marked resolved, and Kaseya said it will keep updating its list, most recently moving Spanning to fully patched.

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

Included with any paid plan.

Open the Kaseya report →

More from Kaseya

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

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

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