Live / awork.com / Incident
awork.com: Information PHP vulnerabilities - awork is not affected / PHP-Schwachstellen - awork ist nicht betroffen
awork.com · awork.comCritical outageResolved2026-11-01 21:51 UTC
Public — what happened
Summary
awork.com posted a security notice, which it rated critical, about two newly disclosed PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619). The company said its assessment found that awork is not affected, because neither its application nor the infrastructure it manages uses PHP. It told customers they do not need to do anything, and said it would keep watching developments. The notice began on 2026-10-21 and is now marked resolved.
Affected
Web-App
Timeline
- Started — 2026-10-21 07:30 UTC
- Monitoring — 2026-10-22 13:24 UTC
- Resolved — 2026-11-01 21:51 UTC · 12 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 awork.com 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 awork.com: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the awork.com report →
More from awork.com
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.