Live  /  Uniweb  /  Incident

Uniweb: Sikkerhetsoppdatering av PHP (CVE-2026-109618 og CVE-2026-109619)

Uniweb · uniweb.noMinor incidentResolved2026-10-23 12:46 UTC
Public — what happened

Summary

Uniweb said it learned of two critical security flaws in PHP and, from 21 October 2026 at 13:18 UTC, put temporary protections on its web hosting platform while waiting for fixes. It said these protections could make some file uploads fail, hide upload progress bars, pause calendar and contact syncing to phones and email programs, and for some customers switch off the phpMyAdmin database tool. Uniweb reported that the security update was installed on newer PHP versions on 21 October and on older ones later that day, that the upload blocking was removed on 22 October, and that phpMyAdmin came back and was reinstalled as an extra precaution. The incident is marked resolved on 23 October at 12:46, and its last posted update said the update was installed on all WP.one clusters.

Affected

Web, WP.one - Web, phpMyAdmin

As listed on Uniweb’s status page.

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

Included with any paid plan.

Open the Uniweb report →

More from Uniweb

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

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

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