{"id":2659,"date":"2026-11-19T21:23:32","date_gmt":"2026-11-19T21:23:32","guid":{"rendered":"https:\/\/allcloudhost.net\/blogs\/?p=2659"},"modified":"2026-11-19T21:24:32","modified_gmt":"2026-11-19T21:24:32","slug":"php-security-release-8-5-13-8-4-28","status":"publish","type":"post","link":"https:\/\/allcloudhost.net\/blogs\/php-security-release-8-5-13-8-4-28\/","title":{"rendered":"PHP Security Release: 8.5.13, 8.4.28, 8.3.37 and 8.2.36"},"content":{"rendered":"<p><em>As of 2026-11-19 UTC. The PHP team released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19, 2026, and calls each one a security release on the <a href=\"https:\/\/www.php.net\/\" target=\"_blank\" rel=\"noopener\">php.net news page<\/a>. The fixes are listed in the <a href=\"https:\/\/www.php.net\/ChangeLog-8.php\" target=\"_blank\" rel=\"noopener\">PHP 8 changelog<\/a>.<\/em><\/p>\n\n<div class=\"wp-block-rank-math-toc-block\"><nav aria-label=\"Table of contents\">\n<ul>\n<li><a href=\"#announcement\">What the PHP security release announcement says<\/a><\/li>\n<li><a href=\"#fixes\">What the changelog lists for the PHP security release<\/a><\/li>\n<li><a href=\"#versions\">Which versions got which fixes<\/a><\/li>\n<li><a href=\"#components\">What the components in the PHP security release are<\/a><\/li>\n<li><a href=\"#unconfirmed\">What the PHP security release pages do not say<\/a><\/li>\n<li><a href=\"#ask-your-host\">What to ask your host<\/a><\/li>\n<\/ul>\n<\/nav><\/div>\n\n<h2 id=\"announcement\">What the PHP security release announcement says<\/h2>\n<p>On November 18, the PHP security team posted a notice titled \"Upcoming Critical PHP Security Release.\" It said the releases were scheduled for Thursday, 19 November 2026, between 14:00 and 14:30 UTC, and that they \"will address security vulnerabilities affecting all supported PHP versions.\" The notice gives the highest severity as CRITICAL and adds: \"The issues rated CRITICAL require either non-default configuration or uncommon setups.\"<\/p>\n<p>It also told users to be ready: \"Users are strongly encouraged to prepare to upgrade promptly once the releases become available.\" On November 19, php.net announced four releases. Each announcement says \"This is a security release,\" and each tells users of that branch to upgrade, for example: \"All PHP 8.5 users are encouraged to upgrade to this version.\" The four releases are new patch versions in the 8.5, 8.4, 8.3 and 8.2 branches.<\/p>\n\n<h2 id=\"fixes\">What the changelog lists for the PHP security release<\/h2>\n<p>The PHP 8 changelog gives each security fix a short description and a CVE identifier. Counting the distinct CVE identifiers in each version's section, the changelog lists 18 for PHP 8.5.13, 14 for 8.4.28, 13 for 8.3.37 and 12 for 8.2.36. The changelog does not say how serious each one is. Here are entries that name components a web host runs:<\/p>\n<ul>\n<li>PHP-FPM: \"PHP-FPM epoll use-after-free can lead to local privilege escalation\" (CVE-2026-129291), \"PHP-FPM request smuggling through an unread HTTP request body\" (CVE-2026-129289), and \"PHP-FPM status endpoint XSS via unescaped user and script fields\" (CVE-2026-129292).<\/li>\n<li>PHP-CGI: \"PHP-CGI out-of-bounds read and write during PATH_INFO correction\" (CVE-2026-129538).<\/li>\n<li>Date: \"Timezone cache use-after-free can lead to remote code execution\" (CVE-2026-129496).<\/li>\n<li>Sessions: \"Partially overwritten session files can lead to remote code execution\" (CVE-2026-126714) and \"Session serializer mismatch can lead to remote code execution\" (CVE-2026-115560).<\/li>\n<li>PHAR: \"PHAR OpenSSL signature bypass via algorithm downgrade\" (CVE-2026-128090).<\/li>\n<li>SOAP: \"SOAP information disclosure through malformed array dimensions\" (CVE-2026-15353).<\/li>\n<li>Standard (URL and HTTP handling): \"Mixed-case HTTPS and FTPS URLs can expose data in plaintext\" (CVE-2026-128064) and \"Denial of service through folded HTTP response headers\" (CVE-2026-127960).<\/li>\n<\/ul>\n<p>Several entries describe what a flaw could lead to. They do not say that any flaw was used against a real site.<\/p>\n\n<h2 id=\"versions\">Which versions got which fixes<\/h2>\n<p>Each of the CVE identifiers listed above appears in the changelog entries for all four releases: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. A few fixes appear in fewer of them. The changelog lists the DOM fix \"Double free during DOM XML serialization\" (CVE-2026-129501) for 8.5.13 and 8.4.28 only. The session fix \"Use-after-free after interrupted session shutdown\" (CVE-2026-129481) appears for 8.5.13, 8.4.28 and 8.3.37 but not 8.2.36.<\/p>\n<p>Four identifiers appear only under 8.5.13: CVE-2026-129182, CVE-2026-129438, CVE-2026-129474 and CVE-2026-48841. One of them is \"Use-after-free in magic method backtraces can lead to remote code execution\" (CVE-2026-129474). The 8.5.13 entry for CVE-2026-48841 reads \"Upgrade to uriparser 1.0.3.\" These fixes are listed under the new patch versions, so the patch number is a useful first check for this PHP security release. Some hosts install PHP from operating-system packages that include security fixes without changing to these exact numbers, so if your version looks older, ask your host whether these fixes are included. (General hosting knowledge, not from the cited pages.)<\/p>\n\n<h2 id=\"components\">What the components in the PHP security release are<\/h2>\n<p>Several of the entries above name parts of PHP that a non-developer may not know. PHP-FPM is a process manager that runs PHP code for a web server. Sessions are how PHP remembers a visitor between page loads. SOAP is a protocol some plugins and older integrations use to talk to other services. PHAR is a packaging format for bundles of PHP code. (This is general PHP knowledge, not from the cited pages.) Whether your site uses any of them depends on how your host and your plugins are set up, which is a question for your host or developer.<\/p>\n<p>The same news page also lists \"PHP 8.6.0 Released!\" on November 19, 2026. That is a separate release from the four patch releases above. This article does not claim that PHP 8.6.0 contains or lacks any of these fixes, because the pages as saved for this article do not say.<\/p>\n\n<h2 id=\"unconfirmed\">What the PHP security release pages do not say<\/h2>\n<p>The php.net news page and the changelog do not say whether any of these flaws was exploited before the fix. They do not say which entry carries the CRITICAL rating: the announcement gives only the highest severity, and the changelog entries carry no ratings. They also do not say how many sites are affected. The announcement says the CRITICAL issues need non-default configuration or uncommon setups, so it does not describe every site as exposed.<\/p>\n<p>The four announcements cover PHP 8.5, 8.4, 8.3 and 8.2. The pages as saved for this article do not mention older branches. If your site runs an older PHP version, check with your host or the PHP project whether it is still supported, because this article cannot tell you.<\/p>\n\n<h2 id=\"ask-your-host\">What to ask your host<\/h2>\n<p>You usually cannot patch PHP yourself on shared hosting; your host does. (This is general hosting knowledge, not from the cited pages.) Questions worth asking about this PHP security release:<\/p>\n<ul>\n<li>Which PHP version and patch level does my site run, and does it include the fixes released on November 19 (8.5.13, 8.4.28, 8.3.37 or 8.2.36, or an equivalent patched package)?<\/li>\n<li>Do you apply PHP patch releases automatically, and how soon after they ship?<\/li>\n<li>If the site runs on its own server, who is responsible for updating PHP on it?<\/li>\n<\/ul>\n<p>On a VPS or dedicated server the update usually falls to you or your developer (general hosting knowledge, not from the cited pages), which is one of the points in our comparison of <a href=\"https:\/\/allcloudhost.net\/blogs\/managed-vs-unmanaged-vps-hosting\/\">managed and unmanaged VPS hosting<\/a>. If you are also thinking about a larger version move, see our post on <a href=\"https:\/\/allcloudhost.net\/blogs\/php-8-6-wordpress-hosting-what-to-ask\/\">the newest PHP release and WordPress hosting<\/a>, and our post on the <a href=\"https:\/\/allcloudhost.net\/blogs\/wordpress-7-1-5-security-release-check\/\">latest WordPress security release<\/a> for the separate WordPress update.<\/p>\n\n<p data-acm-image-credit=\"1\">Featured image: \"The first web-server, data-centre, CERN, Geneva\" by Cory Doctorow (gruntzooki), licensed <a href=\"https:\/\/creativecommons.org\/licenses\/by-sa\/2.0\/\" target=\"_blank\" rel=\"noopener\">CC BY-SA 2.0<\/a>, via <a href=\"https:\/\/www.flickr.com\/photos\/37996580417@N01\/2711081084\" target=\"_blank\" rel=\"noopener\">www.flickr.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"As of 2026-11-19 UTC. The PHP team released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19, 2026, and calls each one\u2026","protected":false},"author":2,"featured_media":2658,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":1,"rank_math_title":"PHP Security Release: What the November Patches Fix","rank_math_description":"The November 19 PHP security release fixes PHP-FPM, session, SOAP and PHAR issues in 8.2 to 8.5. Here is what the changelog lists and what to ask your host.","rank_math_focus_keyword":"PHP security release","rank_math_canonical_url":"","rank_math_robots":[],"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2659","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-webhosting"],"_links":{"self":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts\/2659","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/comments?post=2659"}],"version-history":[{"count":0,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/posts\/2659\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/media\/2658"}],"wp:attachment":[{"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/media?parent=2659"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/categories?post=2659"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/allcloudhost.net\/blogs\/wp-json\/wp\/v2\/tags?post=2659"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}