PHP published security releases on 19 November 2026. Website owners should identify the package serving each application, confirm a supported remediation with their host, deploy it and verify the running processes. Updating a package is one part of the response; it does not prove that an application was never compromised.
Which releases did the PHP project announce?
The official PHP news archive identifies these security releases dated 19 November. They are the releases covered by this article, not a promise that the numbers will remain the newest versions indefinitely.
| PHP branch | Announced security release |
|---|---|
| 8.2 | 8.2.36 |
| 8.3 | 8.3.37 |
| 8.4 | 8.4.28 |
| 8.5 | 8.5.13 |
The project's preceding notice described the highest severity as critical and noted configuration-dependent exposure. That does not establish that every website is exploitable. Check the current vendor advisory and your actual environment rather than converting a severity label into a claim that your own site has been breached.
Start with the runtime that answers web requests
A package listed in a control panel, a command-line version and the runtime handling visitors can differ. Make the first task an evidence collection exercise. Record the website, hosting service, runtime branch, package source and person responsible for patching.
On managed hosting, ask the provider to confirm the remediation available for that account. On a containerised deployment, record the application image and runtime inside the new running container. If the provider backports security fixes, request its advisory or package-level confirmation; a short upstream version string alone may not describe that package accurately.
Use the website maintenance checklist to keep the inventory and update responsibilities current after this incident window.
Decide who performs each part of the update
Keep responsibility clear enough that two teams cannot both assume the other has finished. The host may supply the package, a developer may check compatibility, and the business may approve the maintenance window.
| Responsibility | Evidence of completion |
|---|---|
| Hosting or infrastructure | Corrected package deployed and relevant services restarted |
| Application maintainer | Important workflows tested against that runtime |
| Operations owner | Error monitoring and recovery steps available |
| Business owner | Enquiries, orders and staff access checked after release |
Do not invent a fixed deadline from the table. Prioritisation depends on the advisory, exposure and available controls. Escalate uncertainty to the person responsible for the environment.
Patch without losing the enquiry journey
Take a usable backup before making changes, and confirm what recovery would involve. Test the candidate runtime in a controlled environment when feasible. Disable accidental customer messages and live financial actions in the test copy.
After deployment, verify the actual web path. Submit an authorised test enquiry, confirm it reaches the expected inbox or CRM, and check the confirmation shown to the visitor. Exercise staff login, file handling and scheduled work. Review application logs without publishing credentials or personal customer data in a support ticket.
Record these results next to the deployed version. A statement that “the server was updated” is incomplete when the website still routes requests to an older process.
What if the site is already behaving strangely?
Unexpected redirects, unfamiliar administrator accounts or changed files require investigation as well as patching. Preserve the evidence you need before overwriting the environment. Restrict affected access where appropriate and involve a qualified responder if the scope is unclear.
Our PHP incident-response guide covers a recovery-oriented process. Its older incident context should not be treated as proof that the November releases concern the same vulnerabilities. Likewise, a clean homepage after an update does not establish that every file and credential is trustworthy.
Keep patching separate from a PHP 8.6 adoption project
A new language branch can require additional compatibility work. Make the urgent patch decision against the relevant supported package, then plan a broader migration using its own tests. The PHP version lifecycle guide and WordPress compatibility checklist address those longer-lived decisions.
Frequently asked questions
Do we have to move every application to PHP 8.6 immediately?
The immediate objective is the appropriate security remediation for the affected environment. A feature-branch migration needs a separate compatibility assessment and deployment plan.
Does a successful update prove we were not attacked?
No. It changes the software going forward. Evidence of prior access, file changes or credential exposure needs its own investigation.
What should we ask our hosting provider?
Ask which runtime serves the website, which corrected package is deployed, whether services have been restarted, and what evidence or advisory confirms the remediation. Request a maintenance plan if it is still pending.
Keep a short completion record
Save the advisory checked, package evidence, deployment identifier, responsible people and business-workflow results. RKWS's IT services can help assess the maintenance scope. Share the stack and symptoms through the contact page; never send passwords in an ordinary enquiry message.
