Daily · Article 01 · 4 min read
- Security
PHP security fixes are out. Check which build serves your site
November 19 security releases (JST)
Summary
PHP released fixes on November 19. Find the release for your running branch and confirm the package and application time at your site.
Key facts
PHP, the software that runs many websites' programs on a server, released security updates on November 19. The earlier notice now has four concrete update targets for existing branches: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. PHP also released 8.6.0, the first stable release in a new branch. PHP changelog · 8.6 release
The fixes include critical problems in PHP's handling of session data, which helps a site remember a visitor between requests. The maintainer's advisory for CVE-2026-126714 lists the four fixed versions above. Whether a particular installation is exposed depends on how the application and runtime are configured. The release information establishes what was fixed. It does not establish exploitation or patch application at an individual site. PHP advisory
Hosting provider Cloudways said at 00:24 on November 20 in Japan and Korea that it was automatically rolling out patches within each server’s current PHP branch. It called for no customer action on Flexible or Autonomous. AWS has made packages available for Amazon Linux 2023. Operators of their own servers still need to apply the package and verify the running service. Cloudways status · AWS bulletin

1. Why a website stores a session
Imagine a small shop where you sign in and then open your order history. Each page is a separate request. A session lets the application retain data between those requests, such as the identity it assigned when you signed in. With file-based sessions, the runtime saves that data in a file on the server and reads it back when needed.
One critical fix concerns inconsistent data left by an incomplete save. The advisory describes possible server-side code execution when the required application conditions also hold. For a site owner, the practical question is which session storage the site actually uses and who manages the PHP runtime. File storage is PHP's default, so the setup should be checked even when the team does not remember changing it. Session documentation
The cat asks Q&A
- The researcher
Will updating the shop plugin fix the session handling underneath it?
Pocket NotebookThe fix is in PHP itself. Ask the host which PHP branch serves the shop and what package includes the fix for that branch.
2. Pick the fixed release for the branch your site runs
The first two numbers identify the branch. A small organization using upstream PHP 8.4.27 would compare it with 8.4.28. It can plan the same-branch update and test sign-in and checkout before separately considering a move to 8.6. Hosting and operating-system vendors can backport fixes to package builds with different version labels. Ask those suppliers for the package identifier and advisory mapping.
| Web PHP branch | November 19 upstream release | What to compare |
|---|---|---|
| 8.2 | 8.2.36 | The running 8.2 build and supplier fix record |
| 8.3 | 8.3.37 | The running 8.3 build and supplier fix record |
| 8.4 | 8.4.28 | The running 8.4 build and supplier fix record |
| 8.5 | 8.5.13 | The running 8.5 build and supplier fix record |
| 8.6 | 8.6.0 stable | Compatibility and test results if moving branches |
- Web PHP branch
8.2
- November 19 upstream release
- 8.2.36
- What to compare
- The running 8.2 build and supplier fix record
- Web PHP branch
8.3
- November 19 upstream release
- 8.3.37
- What to compare
- The running 8.3 build and supplier fix record
- Web PHP branch
8.4
- November 19 upstream release
- 8.4.28
- What to compare
- The running 8.4 build and supplier fix record
- Web PHP branch
8.5
- November 19 upstream release
- 8.5.13
- What to compare
- The running 8.5 build and supplier fix record
- Web PHP branch
8.6
- November 19 upstream release
- 8.6.0 stable
- What to compare
- Compatibility and test results if moving branches
The cat asks Q&A
- The researcher
Do I need to move an 8.4 site to 8.6 to get this fix?
Pocket NotebookPHP published a fixed release in the 8.4 branch. Plan around the supported branch actually in use, and evaluate a branch migration as a separate change.
3. Follow the release through to the live website
The illustration shows the handoff from the announcement to the package and then to the production check. The last panel is the evidence the site operator still needs to obtain. Its clock symbolizes scheduling.

The cat asks Q&A
- The researcher
The package is available on my host. Is our checkout already protected?
Pocket NotebookAsk for the version or package that is serving your actual domain and when the host applied it. After the change, check that sign-in, a session across pages and checkout still work.
4. Evidence at each handoff
| Stage and owner | Evidence at the reporting cutoff | What to check next |
|---|---|---|
| Advance notice · PHP security team | Confirmed · November 18 notice | Read the release and conditions now available |
| Fixed release · PHP project | Confirmed · November 19 changelog | Identify the release for the branch in use |
| Package offered · host or OS vendor | Cloudways automatic rollout underway · Status / Amazon Linux 2023 packages available · AWS bulletin | Request a package identifier and fix record |
| Production application · site operator | Unverified per site | Confirm live build, deployment time and functional checks |
- Stage and owner
Advance notice · PHP security team
- Evidence at the reporting cutoff
- Confirmed · November 18 notice
- What to check next
- Read the release and conditions now available
- Stage and owner
Fixed release · PHP project
- Evidence at the reporting cutoff
- Confirmed · November 19 changelog
- What to check next
- Identify the release for the branch in use
- Stage and owner
Package offered · host or OS vendor
- Evidence at the reporting cutoff
- Cloudways automatic rollout underway · Status / Amazon Linux 2023 packages available · AWS bulletin
- What to check next
- Request a package identifier and fix record
- Stage and owner
Production application · site operator
- Evidence at the reporting cutoff
- Unverified per site
- What to check next
- Confirm live build, deployment time and functional checks
The cat asks Q&A
- The researcher
If Cloudways updates automatically, what should I look for on my own site?
Pocket NotebookConfirm the rollout status for your plan. After it completes, check the PHP build handling web requests and the apply time, then verify sign-in and checkout.
To close
Confirm the runtime serving your domain
Start with the existing branch, the supplier's fix record and a backup you can restore. On a site with several servers, confirm the running PHP build on every server that handles visitors.
Sources
- November 19 changelogphp.net
- 8.6.0 stablephp.net
- PHP advisorygithub.com
- Statusstatus.cloudways.com
- AWS bulletinaws.amazon.com
- Session documentationphp.net
- 8.2.36php.net
- 8.3.37php.net
- 8.4.28php.net
- 8.5.13php.net
- November 18 noticephp.net