security release
2 articles with this tag
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 (19 November 2026): 18 fixes, 7 critical, including PHP-FPM request smuggling (CVSS 9.2). What to do today
On 19 November 2026 the PHP team released the security releases PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The 8.5.13 ChangeLog lists 18 fixes with CVE numbers (17 are GitHub security advisories; one is an update of the bundled uriparser library). Seven are rated Critical in GitHub advisories, and the CVE.org records give all seven a CVSS v4.0 score of 9.2. One of them, PHP-FPM request smuggling (CVE-2026-129289), affects every branch from 8.2 to 8.5. The record says that when the front-end server reuses connections to PHP-FPM (for example nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on, neither of which is the default), an unauthenticated remote attacker can forge a backend request, which can lead to execution of PHP code. A timezone cache use-after-free (CVE-2026-129496) and two session issues (CVE-2026-126714, CVE-2026-115560) are also described as able to lead to code execution. CVE-2026-115560 is the third issue disclosed after October's emergency update, and it is fixed now. Fix counts per branch: 18 in 8.5.13, 14 in 8.4.28, 13 in 8.3.37 and 12 in 8.2.36. PHP 8.2 security support ends on 31 December 2026, and 8.1 and earlier have no official fix. PHP 8.6.0 was released the same day. This site's conclusion: update to the latest release of your branch (8.5.13, 8.4.28, 8.3.37 or 8.2.36), check the front-end configuration if you use PHP-FPM, and confirm what your host or container image has applied.
WordPress 7.1.5 security release (18 November 2026): 20 fixes, including unauthenticated privilege escalation, multisite takeover and two SQL injections. What site owners should do today
On 18 November 2026 the WordPress team released 7.1.5, a short-cycle security release with 20 security fixes. The official list includes an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution, a multisite privilege escalation that lets a site Administrator take over a Super Admin account, two SQL injections, unauthenticated stored XSS through shortcode attributes in comments, a denial of service through batched XML-RPC pingbacks, and REST API information disclosures. Fixes are being backported to all branches eligible for security fixes (currently through 4.7) and will ship as each is ready. WordPress 6.9.12 and earlier also received the removal of 1024-bit certificates from the bundled root certificates. WordPress recommends updating immediately. This site's conclusion: update to 7.1.5 (or the latest release of your branch) in the dashboard and confirm that auto-updates actually ran.