Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

PHP Releases Security Fixes Across Supported Branches, Including Critical RCE Issues

PHP released security fixes on November 19: 8.5.13, 8.4.28, 8.3.37 and 8.2.36. Administrators should review the affected configurations and update.

PHP Releases Security Fixes Across Supported Branches, Including Critical RCE Issues
PUBLISHED UPDATED November 19, 2026 at 1:37 PM EST

Update — November 19: Security releases now available

The PHP project has now published PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security updates. Its official November 19 release announcements supersede the pre-release notice below. Security reporting identifies fixes for 18 vulnerabilities, including critical issues whose exploitability depends on configuration.

A reported high-impact example is CVE-2026-129289, a PHP-FPM request-smuggling flaw with possible remote code execution where backend connections are reused; standard configurations without that reuse are not equivalent. See the November 19 technical coverage and the vendor changelog. Operators should confirm the PHP release actually running in web and background services, update through their supported package channels, and review configurations against the vendor descriptions. PHP 8.6.0 was also released today as a new major language version; deploying it is a separate compatibility decision, not an automatic substitute for maintenance on an existing supported branch.

PHP has scheduled security releases for November 19, 2026, between 14:00 and 14:30 UTC—09:00–09:30 EST. Its November 18 preannouncement says vulnerabilities affect all supported branches, with the most serious rated critical.

The critical issues require a nondefault configuration or an uncommon setup. PHP says technical details and fixed version numbers will accompany the releases. At this November 19 morning check, those releases are still scheduled for later today; this report does not identify a released fix or an announced CVE number.

PHP’s support table currently places 8.4 and 8.5 in active support, with 8.2 and 8.3 receiving security fixes. PHP 8.2’s security support ends on December 31, 2026.

IPCRIME analysis: prepare the upgrade now

A useful first step is an inventory of the PHP runtime actually serving each application. Record the branch, package supplier, extensions and deployment owner. Include background workers, command-line jobs and container images in that inventory so the maintenance plan covers more than the public web server.

Prepare a staging check around the functions that matter to the business: authentication, uploads, scheduled jobs and database writes. Confirm that backups can be restored and that someone owns the rollback decision. These steps can be completed before the vulnerability details arrive without guessing which setting makes an installation vulnerable.

Once the releases appear, compare the official affected conditions with the configuration of each service. Follow the security update supplied for that supported branch or the distribution’s documented package update. A visible version string alone may be insufficient when a supplier backports security changes; record the relevant supplier notice alongside the deployed package.

Keep the deployment record specific: what was updated, which services restarted, which checks passed and what remains outstanding. Teams relying on managed hosting should request a concrete update status from their provider. This new preannouncement is separate from our earlier PHP2Shell coverage; its eventual release notes will determine the new issues and remedies.

Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.