Live / Alloy / Incident
Alloy: Security Advisory Notice: Alloy Unaffected by Reported PHP Vulnerabilities
Alloy · alloy.comResolved2026-10-27 18:36 UTC
Public — what happened
Summary
Alloy posted a security advisory on its status page on October 22, 2026, saying its products and services are not affected by two reported PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619. The company said it does not use PHP or depend on it, and that it reviewed its systems ahead of time to confirm this. Alloy also said its infrastructure provider, AWS, stated in a security bulletin that its own services are not impacted. The notice was marked resolved on October 27, 2026, and Alloy rated its severity as none.
Timeline
- Started — 2026-10-22 16:30 UTC
- Investigating — 2026-10-22 16:30 UTC
- Monitoring — 2026-10-22 16:31 UTC
- Resolved — 2026-10-27 18:36 UTC · 5 days 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 Alloy 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 Alloy: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Alloy report →
More from Alloy
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.