Versions 6.1.3, 6.0.10 and 5.2.19 carry the fixes. The one moderate issue is a GeoJSON request forgery, and full protection for another GIS flaw needs GDAL 3.9.
PHP security releases fix up to 18 flaws across all supported branches
EditorialBy TrustList Editorial
The PHP project shipped security releases 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on 19 November 2026, fixing flaws in sessions, the timezone cache, SOAP, Phar signatures and PHP-FPM, the same day PHP 8.6.0 came out.
- Cybersecurity
- Application Security
- Web Development
About PHP security releases fix up to 18 flaws across all supported branches
PHP security releases fix up to 18 flaws across all supported branches
19 November 2026: The PHP development team released PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 and calls each of them a security release. Every supported branch is affected, and the project asks all users of each branch to upgrade. On the same day it released PHP 8.6.0, a new major version, so teams planning the upgrade now have a choice between the patch for their branch and a move to 8.6.
Not yet independently verified. Version numbers, advisory titles and CVE numbers come from the PHP project's own ChangeLog and release announcements of 19 November 2026, read on 20 November. The PHP project does not give severity scores in its changelog and does not say whether any of these flaws has been exploited; we have not checked each CVE record. We will update this when it can be confirmed, and remove this note.
What is fixed
The ChangeLog lists the fixes by GitHub security advisory and CVE number. The ones shared by all four branches include:
- Session: partially overwritten session files can lead to remote code execution (CVE-2026-126714), and a session serializer mismatch can lead to remote code execution (CVE-2026-115560). Session IDs are now validated in full instead of stopping at the first NUL byte.
- Date: a timezone cache use-after-free that can lead to remote code execution (CVE-2026-129496).
- PHP-FPM: request smuggling through an unread HTTP request body (CVE-2026-129289), cross-site scripting on the status page through unescaped user and script fields (CVE-2026-129292), and an epoll use-after-free that can lead to local privilege escalation (CVE-2026-129291).
- PHP-CGI: an out-of-bounds read and write during PATH_INFO correction (CVE-2026-129538).
- Phar: an OpenSSL signature bypass through algorithm downgrade (CVE-2026-128090).
- SOAP: information disclosure through malformed array dimensions (CVE-2026-15353) and a use-after-free when processing DTD entity references (CVE-2026-129506).
- Standard library: mixed-case HTTPS and FTPS URLs can expose data in plaintext (CVE-2026-128064), and folded HTTP response headers can cause a denial of service (CVE-2026-127960).
PHP 8.3.37, 8.4.28 and 8.5.13 also fix a use-after-free after an interrupted session shutdown (CVE-2026-129481). PHP 8.4.28 and 8.5.13 fix a double free during DOM XML serialization (CVE-2026-129501). PHP 8.5.13 alone fixes two engine use-after-free flaws, one in magic method backtraces that can lead to remote code execution (CVE-2026-129474) and one after shutdown (CVE-2026-129182), plus two in its URI extension, including an upgrade to uriparser 1.0.3 (CVE-2026-48841 and CVE-2026-129438).
Which branches are still supported
According to the project's supported versions page, PHP 8.2 receives security fixes until 31 December 2026, so 8.2.36 is one of its last releases. PHP 8.3 is supported for security until 31 December 2027, 8.4 until 31 December 2028 and 8.5 until 31 December 2029. PHP 8.6, released on 19 November, has active support until 31 December 2028.
Upgrade, then restart PHP-FPM
Teams running PHP-FPM behind a web server, or applications that rely on PHP sessions, SOAP or Phar archives, have the most direct exposure. Upgrade to the fixed release for your branch, then restart PHP-FPM so the new build is loaded. Operating system and hosting packages usually follow the upstream release within days, so check your distribution's own advisory for the package version that carries these fixes. Sites still on PHP 8.2 should plan their move to a newer branch before support ends at the end of December.
Sources
- PHP 8 ChangeLog (8.5.13, 8.4.28, 8.3.37, 8.2.36), 19 November 2026
- php.net release announcements, 19 November 2026, 19 November 2026
- PHP supported versions, 20 November 2026
Categories & features
- Cybersecurity
- Application Security
- Web Development
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
FoxIO found seven of ten HTTP/3 stacks open to header amplification. quic-go, Cloudflare quiche, lsquic and Wireshark are fixed; Bun, the h3 crate and aioquic are not, and a proof of concept is public.
CVE-2026-114509 lets an attacker with no token log in as an existing user on apps using TokenGuard with MySQL or MariaDB. Upgrade to 13.29.0 or 12.68.0; a proof of concept is public.
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 close CVE-2026-109618 and CVE-2026-109619. Every PHP install serving web requests is at risk, mod_php most of all, and PHP 8.1 and older get no official fix.
Google announced the removal a year ago; the XSLTEnabled enterprise policy and an origin trial keep it working only until Chrome 176, due on 17 August 2027.
Edge 159 disables the XSLTProcessor API and XSL stylesheet instructions by default. A temporary XSLTEnabled policy buys time until Edge 176 in summer 2027.
SA-CORE-2026-014 scores 19 out of 25. Sites on 11.2 or 10.5 and older have no patch; uninstalling the Field UI module blocks the flaw until an upgrade is possible.
One flaw sits in image optimisation of SVG files and reaches back to Next.js 10; the other hits the use cache directive in 16.x and has no workaround. A third advisory fixes a Server Actions denial of service.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.