Our blog on today’s PHP vulnerabilities is live.
If you’re a customer running PHP, you may need to take action yourself. Our teams are working across our platform, and the steps are here: digitalocean.com/blog/critical-…
If you’re a customer running PHP, you may need to take action yourself. Our teams are working across our platform, and the steps are here: digitalocean.com/blog/critical-…
Oct 21, 2026 · 9:50 PM UTC
5
3
17
3,856
@digitalocean The wrong version still gets installed following these steps.
1
0
0
135
@CyllianForsakenk you for flagging this.
We apologize for the inconvenience and would kindly ask you to submit a Ticket using the link below for us to have this reviewed further.
digitalocean.com/company/contac…
Please share your Email address and the Ticket details in a Direct message as well.
If you have any other questions please feel free to reach out.
We apologize for the inconvenience and would kindly ask you to submit a Ticket using the link below for us to have this reviewed further.
digitalocean.com/company/contac…
Please share your Email address and the Ticket details in a Direct message as well.
If you have any other questions please feel free to reach out.
0
0
0
134
@digitalocean You skipped the designated security releases 8.5.6, 8.5.8, and 8.5.9 and kept users on 8.5.2 (15 Jan 2026).
Will you keep this practice going forward?
Will you keep this practice going forward?
0
0
1
91
@digitalocean Straight from your (failing) build logs:
For reference, the following runtimes are currently available: PHP: 8.5.3, 8.5.2, 8.5.1, 8.5.0, 8.4.18, 8.4.17, 8.4.16, ...
Where are 8.5.12 and 8.4.27?
For reference, the following runtimes are currently available: PHP: 8.5.3, 8.5.2, 8.5.1, 8.5.0, 8.4.18, 8.4.17, 8.4.16, ...
Where are 8.5.12 and 8.4.27?
1
0
0
154




