PHP 8.5.13 is out: update PHP, then check one setting
PHP shipped security builds for 8.2 to 8.5 on 19 November 2026. Confirm your site runs the fixed build, then decide on the upload progress setting.
The short answer
On 19 November 2026 PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36, and each is described as a security release that users of that branch should install. The 8.5.13 changelog fixes two session bugs that can lead to remote code execution, CVE-2026-115560 and CVE-2026-126714, the first being the issue behind PHP's October advice to set `session.upload_progress.enabled` to 0. Update first, confirm the web server runs the new build, and keep upload progress switched off if your sites do not use upload progress bars.
Reading options
On this page
PHP shipped security builds for four branches on 19 November 2026: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. If your site runs any of them, you want the new build, and you want to look at one session setting that PHP told everyone to switch off back in October. This guide walks through both jobs.
The day before, PHP's security team posted a warning that the release would land between 14:00 and 14:30 UTC and that the highest severity was critical. The same post said the critical issues "require either non-default configuration or uncommon setups", so this is a calm update, not a fire drill. Still, the 8.5.13 changelog lists session bugs that can lead to remote code execution, and sessions run on almost every login form on the web.
By the end you will know which PHP build your website really runs, how to get the fixed one, how to read and set session.upload_progress.enabled, and how to prove both changes worked.
What this release actually is
A PHP security release is a patch version inside the same branch. Going from 8.5.12 to 8.5.13 keeps you on PHP 8.5 and brings in fixes. Going from 8.4 to 8.5 is a different, bigger job, because a new branch can change how the language behaves.
Think of it like a recall notice for your car brakes. The car is the same model, you keep driving it the same way, but the garage swaps a part you cannot see.
The changelog is the list of what changed. For 8.5.13, the Session section on the PHP changelog lists these security fixes:
- CVE-2026-115560: session serializer mismatch can lead to remote code execution.
- CVE-2026-126714: partially overwritten session files can lead to remote code execution.
- CVE-2026-129481: use-after-free after interrupted session shutdown.
Other sections of the same 8.5.13 entry list more fixes, for example CVE-2026-129474 (use-after-free in magic method backtraces) and CVE-2026-129496 (timezone cache use-after-free), both described as able to lead to remote code execution. The FPM section lists CVE-2026-129291 (epoll use-after-free, local privilege escalation), CVE-2026-129289 (request smuggling through an unread request body) and CVE-2026-129292 (XSS on the FPM status endpoint). A use-after-free is a bug where code keeps using memory after handing it back, which attackers can sometimes turn into running their own code.
Heads up: I read the 8.5.13 section of the changelog closely. I did not confirm that 8.4.28, 8.3.37 and 8.2.36 carry the exact same list, so check your own branch's section on the PHP 8 ChangeLog before you quote it to anyone.
The setting in this story
Session upload progress is a PHP feature that writes the progress of a file upload into $_SESSION while the upload runs. A second request can then read it and draw a progress bar. The setting that controls it is session.upload_progress.enabled, and the PHP manual says it defaults to 1, which means on.
On 23 October 2026, PHP posted an informational advisory suggesting session.upload_progress.enabled=0 "until the next regular bugfix release". The risky case needed an unusual mix: an app that sets session.serialize_handler to php_binary or php_serialize, then switches it to php at runtime with ini_set() before calling session_start(), with upload progress still on. PHP promised a full advisory for CVE-2026-115560 with the next release. That next release is this one, and the 8.5.13 changelog now lists the fix.
Why this matters: the October fix and this one overlap. If you followed earlier advice, you may already have the setting at 0. This guide helps you decide whether to keep it that way.
Before you start
Here is what you need. Most of it takes five minutes to gather.
- A login with enough rights to see or change PHP settings: WHM root or reseller access, a cPanel account, or SSH access to the server.
- Your site's current PHP branch, for example 8.4 or 8.5. You will confirm it in Step 1.
- A backup of the ini file you plan to edit. Step 3 shows how.
- A staging copy of the site if you can, so you can test a
phpinfo()page without exposing it on the live site. - Around 20 to 30 minutes, more if you run many PHP versions.
- Risk level: low for the setting change, low to medium for the PHP update itself. Any software update can surprise you, so have a recent full site backup first.
Quick tip: if you are on shared hosting, you probably cannot install PHP builds yourself. Your job is to check, set the session option for your own account, and ask the host about the update.
Step by step: confirm your build and get the update
Step 1: Check the PHP version on the command line
If you have SSH, this command prints the PHP version of the command line binary.
php -vYou should see a first line that starts with PHP followed by a version number, such as 8.5.12 or 8.5.13. Anything below the patch numbers released on 19 November (8.5.13, 8.4.28, 8.3.37, 8.2.36) means that binary is not updated yet.
Heads up: the command line PHP is often a different binary from the one your website uses. On panels with several PHP versions, each site can run its own. Step 2 checks what the web actually runs.
Step 2: Check the PHP version the website runs
The most reliable check is a phpinfo() page loaded through your website. The PHP manual says phpinfo() prints the PHP version, paths, server information and the master and local values of configuration options. That is a lot of detail to leave public. Use a staging copy, give the file a random name, and delete it right after.
This one-line file prints the full PHP information page when you open it in a browser.
<?php phpinfo();Save it as something like info-7f3k9.php in the site's document root, then open https://example.com/info-7f3k9.php. The version is in the big header at the top. Note the Loaded Configuration File line too, because it tells you which php.ini the web side reads.
Delete the file as soon as you have the numbers.
Step 3: Back up the ini file you will touch
Before any change, copy the current file. On a cPanel server, the WHM docs say the MultiPHP INI Editor saves each version's settings to /opt/cpanel/<php_package>/root/etc/php.ini.
This command makes a dated copy of the PHP 8.5 ini file on a cPanel server (swap ea-php85 for your package name).
cp -a /opt/cpanel/ea-php85/root/etc/php.ini /opt/cpanel/ea-php85/root/etc/php.ini.bak-20261119On other servers, copy the file named on the Loaded Configuration File line from Step 2 instead.
Step 4: Get the new PHP build
How you get the update depends on who builds your PHP.
On cPanel servers, PHP comes from EasyApache 4 packages. At the time of writing (19 November 2026), the newest EasyApache 4 entry I could see in the cPanel release notes was 25.97, dated 18 November 2026. It mentioned PHP 8.6 directive data but did not mention 8.5.13, 8.4.28, 8.3.37 or 8.2.36. I read only the first part of that long page, so treat this as "not confirmed yet" rather than "missing". Check the cPanel release notes again, or ask your host when the packages arrive.
Heads up: do not compile PHP from source on a cPanel server to get ahead of the packages. A hand-built PHP sits outside the EasyApache packages your panel manages and updates, so you would be maintaining it alone from then on.
On a VPS that uses your Linux distribution's packages, update through the normal package manager once your distribution or package repository ships the new build. On managed or shared hosting, the host does this for you.
I could not open the cPanel MultiPHP Manager steps for switching a domain's PHP version today, so I am not giving click paths for that. If a site sits on an old branch, ask your host or follow the cPanel docs for MultiPHP Manager.
Why this matters: a running PHP-FPM service or web server keeps the old build loaded until it restarts. Package updates usually handle that, but always repeat Step 2 afterwards to be sure.
Step by step: decide on and set the upload progress setting
Step 5: Read the current value
This command prints every line of the PHP configuration that mentions upload progress.
php -i | grep -i upload_progressYou should see lines such as session.upload_progress.enabled => On => On. The two values are the local and master values. If it says Off, the setting is already off for the command line.
This command prints just the one value as a number, where 1 means on and an empty result or 0 means off.
php -r 'echo ini_get("session.upload_progress.enabled"), PHP_EOL;'Heads up: both commands show the command line value. The website can have its own value from a different php.ini, a pool config or a .user.ini file. For the real web value, search the phpinfo() page from Step 2 for session.upload_progress.enabled.
Step 6: Decide whether you need upload progress at all
Most sites do not. The feature only does something when a form sends a special hidden field named by session.upload_progress.name and the app reads the progress data back from $_SESSION.
The PHP manual also carries its own warning: upload progress writes the client-supplied file name and field name into the session store, those values are not validated, and in apps without progress bars it says to consider turning the option off.
This command searches your site's code for anything that reads the progress data, which helps you spot a real user of the feature.
grep -rn "upload_progress" /home/exampleuser/public_html --include="*.php"No results usually means nobody uses it. A result inside a plugin or upload library means you should test uploads on staging after the change.
Made-up example: Sara runs three WordPress sites on one VPS. She set session.upload_progress.enabled=0 on 23 October, then wondered on 19 November whether she could switch it back on. Her grep found nothing, her media uploads use their own JavaScript progress, so she left it off and moved on in two minutes.
The October GitHub advisory for CVE-2026-109619 agrees with Sara's choice. It says it "might be prudent" to keep session.upload_progress.enabled=0 if you do not need the feature, even after patching.
Step 7: Set it for a whole PHP version in WHM
If you have root on a cPanel server, open WHM > Software > MultiPHP INI Editor. Choose the Editor Mode tab, pick the PHP version, and add or change this line in the file that loads.
session.upload_progress.enabled = 0Click Save. The setting applies to that PHP version only, so repeat it for every version your sites use. The cPanel docs do not say whether you need to restart PHP-FPM afterwards, so check the result with a phpinfo() page as in Step 2. Restarting PHP-FPM is a general practice if the value has not changed, not something the cPanel docs call for.
Step 8: Set it for one cPanel account
If you only have a cPanel login, open MultiPHP INI Editor in cPanel and choose Editor Mode. Pick Home Directory to cover all your sites, or pick one domain, then add the same line and click Save.
session.upload_progress.enabled = 0The cPanel docs say this tool writes to php.ini, .user.ini and .htaccess, each only where that file supports the directive. Quick tip: the PHP manual says .user.ini files are re-read every 300 seconds by default, controlled by user_ini.cache_ttl, so a change through .user.ini can take up to five minutes to show.
Step 9: Set it on a server without a panel
Because the setting is INI_PERDIR, the PHP manual says you can set it in php.ini, .htaccess, httpd.conf or .user.ini, but not with ini_set() in code. Pick the place that matches how PHP runs.
For a plain php.ini file, add or change this line, then reload PHP-FPM or the web server.
session.upload_progress.enabled = 0For a PHP-FPM pool, the FPM manual says settings made with php_admin_flag cannot be overridden with ini_set(). This line goes in the pool configuration file for the site (its location depends on your distribution or panel), then you reload PHP-FPM.
php_admin_flag[session.upload_progress.enabled] = offFor Apache with PHP as a module, the PHP manual says booleans in .htaccess use php_flag. This line goes in the site's .htaccess file and needs AllowOverride Options or AllowOverride All.
php_flag session.upload_progress.enabled offFor Nginx in front of PHP-FPM, the FPM manual shows PHP settings passed with fastcgi_param. This line goes inside the location block that passes requests to PHP-FPM, then you reload Nginx.
fastcgi_param PHP_ADMIN_VALUE "session.upload_progress.enabled=0";Heads up: the FPM manual warns that these values travel as FastCGI headers, so PHP-FPM must never listen on an address the whole internet can reach. Also, the manual's own example builds several settings into one variable, separated by a newline (\n), before passing it. If you already pass PHP_ADMIN_VALUE for something like open_basedir, add the new setting to that same value instead of adding a second line.
I did not verify DirectAdmin or Plesk steps today. On those panels, look for the PHP settings screen for your domain, or ask your host to set it for you.
How to check it worked
Run these checks after both the update and the setting change.
- Load a fresh
phpinfo()page on staging, as in Step 2. The header should show 8.5.13, 8.4.28, 8.3.37 or 8.2.36 (or newer) for your branch. - On the same page, find
session.upload_progress.enabled. The Local Value column should readOff. If Master Value readsOnbut local readsOff, a per-directory or pool setting is doing the job, which is fine. - Run
php -vandphp -r 'echo ini_get("session.upload_progress.enabled"), PHP_EOL;'again for the command line side, where cron jobs and WP-CLI run. - Upload a test file through the site's real upload form on staging. It should still work. Only the server-side progress tracking is gone.
- Delete every
phpinfo()test file and confirm it now returns a 404.
This command confirms the test file is gone by asking for just the response headers.
curl -I https://example.com/info-7f3k9.phpThe first line should show 404. If it shows 200, the file is still there.
Troubleshooting
The command line still shows the old version
Symptom: the update ran, but php -v still shows 8.5.12 or similar. Likely cause: your shell finds another PHP binary first, or the panel's CLI default points to another version. Fix: run which php and php --ini to see which binary and ini files load, then check the web side with Step 2, which is what visitors hit.
The website still shows the old build
Symptom: the command line shows 8.5.13 but phpinfo() shows 8.5.12. Likely cause: PHP-FPM or the web server has not reloaded, or the site uses a different PHP version package. Fix: restart PHP-FPM for that version (or ask your host), then reload the phpinfo() page.
The setting still reads On
Symptom: you saved session.upload_progress.enabled = 0, but phpinfo() still shows On. Likely causes: you edited a different ini file than the one in Loaded Configuration File, a .user.ini change is still inside its 300 second cache window, or a pool file sets it back. Fix: edit the file the page names, wait five minutes or reload PHP-FPM, and search pool files for upload_progress.
Setting it in code does nothing
Symptom: you added ini_set('session.upload_progress.enabled', '0'); to your code and the value did not change. Likely cause: the setting is INI_PERDIR, so the PHP manual says it cannot be changed at runtime. Fix: remove that line and use one of the methods in Steps 7 to 9.
Upload progress bars stopped moving
Symptom: after the change, a progress bar in your app sits at zero until the upload ends. Likely cause: that app really uses session upload progress. Fix: decide with the developer. Once you run the fixed build, you can turn the feature back on for that one site only, using a per-domain setting, and keep it off everywhere else.
Nginx refuses to reload
Symptom: nginx -t, which checks the configuration syntax, reports an error after you add fastcgi_param. Likely cause: a missing semicolon or quote, or the line sits outside a location block. Fix: copy the line exactly as shown in Step 9, run nginx -t again, and run nginx -s reload only when the test passes.
A few extra notes
The full advisory for CVE-2026-115560 is linked from the 8.5.13 changelog as GHSA-658j-r8rw-q6mx. When I tried to open that GitHub page today, it did not load. Check it again in a few days, because it may add details on affected versions or mitigations.
PHP 8.2 users have another date to watch. The PHP supported versions page lists security support for 8.2 ending on 31 December 2026, 8.3 on 31 December 2027, 8.4 on 31 December 2028 and 8.5 on 31 December 2029. If you are still on 8.2, read our guide on PHP 8.2 security support ending and the walkthrough on checking and switching your PHP version.
If you missed October's critical patch, the same update path covers it, and our October PHP RCE patch guide explains that earlier round.
When to ask for help: if you run a custom app that changes session.serialize_handler at runtime, or you see upload progress code you did not write, ask the developer before you change anything. If you are on shared hosting, ask the host to confirm the patched build is live for your account.
The one message worth forwarding
Copy this and send it to your host or developer.
"Hi, PHP released security builds 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026. Can you confirm when our server will run the patched build for every PHP version our sites use? Also, please confirm session.upload_progress.enabled is set to 0 for our sites, unless one of them really uses upload progress bars. Thanks."
Update the build first, check it through the website, and leave upload progress off unless something actually needs it.
Reader questions
Which PHP versions were released on 19 November 2026?
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The PHP news archive describes every one of them as a security release and asks users of each branch to upgrade.
Do I still need `session.upload_progress.enabled=0` after updating?
The 8.5.13 changelog lists a fix for CVE-2026-115560, the bug the October advice was about. If your sites do not use upload progress bars, keeping the setting at 0 still costs you nothing, and the October GitHub advisory calls that prudent even after patching.
Can I turn off upload progress with `ini_set()` in my code?
No. The PHP manual lists `session.upload_progress.enabled` as `INI_PERDIR`, which means it can be set in php.ini, .htaccess, httpd.conf or .user.ini, but not with `ini_set()` at runtime.
Why does php -v show a different version than my website?
The command line and the web server can use different PHP binaries and different ini files, especially on panels that offer several PHP versions. Trust a phpinfo() page served through the website for what visitors actually hit.
Should I compile PHP 8.5.13 myself on a cPanel server?
No. cPanel servers get PHP through EasyApache 4 packages, and a hand-built PHP sits outside what the panel manages and updates. Wait for the package update or ask your host when it will land.
Is PHP 8.2 still safe to run?
PHP 8.2 gets security fixes until 31 December 2026, according to the PHP supported versions page. After that date it receives no more fixes, so plan a move to 8.3 or newer now.
Was this guide helpful?
Help us make the next update better.
Sources & further reading
- PHP News Archive 2026
- PHP 8 ChangeLog (8.5.13 section)
- PHP manual: Session runtime configuration
- PHP supported versions
- GitHub advisory GHSA-6wmf-4rv5-p3rp (CVE-2026-109619)
- cPanel release notes (EasyApache 4)
- cPanel docs: MultiPHP INI Editor for WHM
- cPanel docs: MultiPHP INI Editor for cPanel
- PHP manual: FPM configuration
- PHP manual: .user.ini files
Originally published . About our editorial updates.



