To protect ibiblio contributors, visitors, and infrastructure, we are preëmptively disabling PHP execution across all publicly accessible ibiblio web assets beginning the morning of Wednesday, October 21, 2026.
This temporary measure applies to any web asset that is exposed through a public IPv4 or IPv6 address, including assets made publicly available through a load balancer.
We are taking this step in response to the PHP security announcement concerning critical vulnerabilities affecting PHP. Public PHP execution will remain disabled until further notice and will be restored once we are confident that appropriate mitigations or updates have been applied.
We understand that disabling PHP may interrupt contributor websites and services. We regret the disruption and will do our best to keep it as brief as possible, but we believe this precaution is necessary while the risks are being addressed.
I have been hosting OER educational resources on ibiblio.org through openbookproject.org since 1999, but over the last few days it has stopped working. What can I do? My students can not access the OER textbooks we use in my class.
Package updates are available for a subset of hosts. We are in process both for applying the updates and validating the safety of restoring sites that rely on those hosts. We estimate 90 minutes to having a subset of PHP sites hosted by ibiblio restored.
Package updates that resolve the PHP vulnerabilities have been applied to vhost and nom cluster hosts. This re-enables access for confluence, nom, whitehouse transition project, and many other collections whose host names do not end in ibiblio.org.
It will take approximately another 90 minutes to validate and enable a further cluster of hosts.
Most, but not all, collections under the ibiblio.org domain are now available. A subset of collections were hosted in a manner that requires additional work to re-enable. We do not yet have a timeline. If you have a collection of the form example.ibiblio.org or ibiblio.org/example, and it currently gives a 403 forbidden error where you believe it should not, please know that we are working to restore additional collections right now, and yours is likely among them. Given the local time, it may be more than ten (10) hours before we have a more precise estimate for time to resolution.
I’m the admin of the OESF forum (www.oesf.org), the site is still not reachable (503 error), I’ll report back when it will be again working. Thanks for your efforts and the prompt response to this security issue.
OESF is one of a small handful of sites that were hosted on a backend that this process has forced us to retire, and the re-deployment of your forum to the new backend is taking longer than we had hoped. The short version is that we will need feedback from you within about a business day, and we have started an RT ticket to track that conversation with you.
Again, we’re sorry for the delay and thank you for your participation in this process.