PHP’s new critical fixes: what African teams need to verify now
PHP, server-side software used to run web applications, addresses code-execution, request-confusion and data-exposure risks in versions 8.2.36, 8.3.37, 8.4.28 and 8.5.13. Exposure depends on configuration, while PHP 8.2 reaches end of security support on 31 December.
Severity
5Affected country
NGSector
Cross-sectorPublished
21 November 2026
Our score measures operational relevance to Africa — not the global virality of the story.

Contents · 6
A new security release, not a repeat of October
The PHP project released four security versions on 19 November 2026: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. They follow October’s critical fixes but address a different set of vulnerabilities across the engine, PHP-CGI, PHP-FPM, sessions, PHAR, SOAP and network streams. PHP 8.6.0, released on the same day, also incorporates fixes applicable to the new branch.
One day earlier, the PHP security team said the highest severity would be critical while noting that the most serious cases required non-default configuration or uncommon setups. That distinction matters. A critical CVE does not mean every WordPress, Drupal, Laravel or custom application is immediately exploitable from the Internet. It is also not a reason to wait. Organisations must identify which PHP interfaces they actually run and which prerequisites are present.
As of 21 November, the public sources reviewed do not establish a global exploitation campaign against this November set. That assessment may change and does not justify postponing updates. The flaws affect a widely deployed component, some permit code execution under specific conditions, and technical details are now public.
Different paths require different priorities
CVE-2026-129538 affects PHP-CGI through an out-of-bounds read and write during PATH_INFO correction. An organisation that does not use traditional CGI does not have the same path to exposure, but it must establish that fact on the server processing real requests. A CMS name or hidden HTTP banner does not answer the question.
CVE-2026-129496 is a use-after-free in the timezone cache that may lead to code execution. Other defects affect error traces and engine shutdown, including CVE-2026-129474 and CVE-2026-129182 on PHP 8.5. Their exploitability depends on an application path capable of triggering the faulty memory state.
PHP-FPM receives several important fixes. CVE-2026-129289 describes request confusion when an HTTP body is not fully consumed; CVE-2026-129291 may allow local privilege escalation; and CVE-2026-129292 affects status-page output. Teams need to inspect the full architecture: reverse proxy, web server, FPM socket, pool privileges and any exposed status endpoint. Updating a command-line package without recycling workers does not prove that live traffic is using new code.
Sessions remain sensitive. CVE-2026-126714 concerns partially overwritten session files, while CVE-2026-115560 concerns serializer mismatch that can lead to code execution in specific configurations. Nigeria’s ngCERT had already issued an alert on the latter on 11 November. The November release now provides a clear upstream response: upgrade, then confirm that the application does not dynamically replace session handlers in an uncontrolled way.
The release also fixes quieter but material failures
The release is not limited to code-execution scenarios. It addresses an OpenSSL signature downgrade in PHAR, memory corruption in SOAP and DOM, denial of service through folded HTTP response headers and possible plaintext exposure when HTTPS or FTPS URL schemes use unusual case. These defects matter to applications that import archives, consume legacy SOAP services or make outbound calls to partners.
That profile exists in African information systems where a modern front end may coexist with payment gateways, public-sector packages, hospital systems or older operator interfaces. These systems are not vulnerable because they are African. Long integration lifetimes, supplier dependence and narrow maintenance windows can, however, extend exposure.
Prioritisation should therefore not rely on the highest score alone. An Internet-facing PHP-FPM service behind NGINX, an internal SOAP application and a forgotten CGI tool have different attack paths. Inventory must connect each domain and scheduled job to its PHP SAPI, active build, extensions, inbound and outbound flows and operational owner.
PHP 8.2 now creates a second decision
PHP 8.2.36 fixes the current set, but the branch reaches end of security support on 31 December 2026, according to PHP’s official schedule. Installing 8.2.36 is therefore an immediate action, not a sustainable plan. Organisations should prepare migration to a supported branch, test extensions and dependencies, and define controlled rollback.
Moving directly to PHP 8.6 may be appropriate after validation, but a major branch released two days ago should not be pushed blindly to a critical service. For many teams, the controlled route is to patch the current branch immediately and then migrate to 8.4 or 8.5 after application testing. The right choice depends on Linux distribution policy, application-vendor support and maintenance commitments.
Distribution packages may backport fixes without reproducing the upstream version number. Conversely, a reassuring container tag may still run an old layer unless the image was rebuilt and redeployed. Evidence needs to cover the supplied build, image digest, active process and worker-recycle time.
A verifiable action plan
Technical leaders should request a short record for every PHP service:
- affected domain or task and named business owner;
- actual execution mode: CGI, FPM, Apache module, CLI or embedded component;
- vendor version and revision loaded by the active process;
- affected extensions and functions, especially sessions, SOAP and PHAR;
- update, restart and functional-validation timestamps;
- preserved logs and anomalies reviewed before closure;
- an exit path for PHP 8.2 and unsupported branches.
Where immediate maintenance is impossible, teams can temporarily reduce exposure by withdrawing an unused endpoint, isolating CGI, restricting an FPM status page, disabling a genuinely unused function or limiting outbound traffic. Every mitigation needs an expiry date. None substitutes for the fixed release.
The conclusion is not that PHP is inherently unsafe
PHP continues to power a significant share of the web and many African public and commercial services. The operational problem is the gap between fast upstream disclosure and local ability to identify the runtime actually serving requests. An organisation does not need a large SOC to respond well if it knows its assets, maintains an update path and demands evidence from hosting providers.
The useful answer on 21 November is specific: these are the affected services, these prerequisites are present or absent, this is the active fixed build, these workers were recycled, and this is the migration plan before PHP 8.2 support ends.
— ◆ —