PHP patches seven critical flaws in November security updates | Magica
PHP fixes seven critical flaws; shared session settings still need review
Editorial Team
••📖9 min read
PHP’s November 19 security releases address seven critical flaws, including unauthenticated code execution through reused backend connections. Patching takes priority, but applications that retain session upload progress must also check shared storage and serialization settings.
Seven critical fixes cover request smuggling, session handling and memory safety, with different prerequisites for exploitation.
Applications retaining session upload progress need consistent serialization settings across shared storage, even after updating.
AWS firewall rules cover only two critical issues and initially count matching traffic rather than block it.
PHP, the server-side programming language used to process website requests, received security updates on November 19 addressing seven critical vulnerabilities. One can let an unauthenticated attacker execute PHP code through a reused backend connection. The PHP security team says the critical issues require non-default configurations or uncommon setups; the advisories show why patching and checking the actual deployment must go together.
The release announcements identify PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 as security releases and urge users of each branch to upgrade. PHP 8.6.0 also became available as a major language update; a report on the fixes says it includes all seven critical patches. Individual flaws affect different version ranges, so the critical count does not mean every branch has all seven defects.
The language’s reach makes the release consequential: technology survey service W3Techs’ November 19 usage survey identifies PHP on 68.1% of websites whose server-side language it can determine. That denominator excludes websites with an unknown language, and the figure measures adoption, not vulnerable installations.
The releases follow October’s patches for two critical flaws involving out-of-memory corruption and stale worker state, collectively called PHP2Shell. The report on November’s fixes describes the October flaws as widely exploited. Two of the new critical advisories address incomplete cleanup fixes from that earlier release, making an October update insufficient for those newly documented paths.
W3Techs reports PHP adoption at 68.1% among websites with a known server-side language on November 19, 2026. This measures usage, not vulnerable installations. Source: W3Techs PHP usage statistics, November 2026.
The management company supporting Japan's Shonan Beauty Clinic network disclosed stolen customer passwords stored without encryption and a separate booking-service incident. Treatment-related submissions were also exposed, while the affected population and financial impact remain under investigation.
Editorial Team
Connection reuse opens a route around the web server
The PHP-FPM request-smuggling flaw, CVE-2026-129289, crosses the boundary between a web server and PHP’s FastCGI Process Manager, which runs PHP workers behind the web server. PHP can leave part of an HTTP request body unread, then accept those remaining bytes as a separate FastCGI request when the backend connection is reused, according to the advisory.
The forged request can bypass front-end routing and change administrator-level PHP settings. With knowledge of an existing PHP script’s path, an attacker can execute code with the PHP worker’s privileges. Changed administrator settings can persist into later requests on that worker. The attack requires neither memory corruption nor a race condition.
Two conditions are central: the front end must retain backend connections, and an application path must open php://input without fully reading it. Relevant settings include nginx’s fastcgi_keep_conn on and Apache’s enablereuse=on. Standard nginx and Apache configurations that close those connections after each request are outside the demonstrated PHP-FPM attack. The advisory says that attack does not require non-default PHP settings; the connection setting belongs to the front end.
The same cleanup defect affects persistent LSAPI connections, another PHP backend interface, but the advisory establishes request-stream disruption there, not the PHP-FPM code-execution mechanism.
Code inspection dates the underlying defect to PHP 5.6.0. Turning off backend connection reuse is the interim mitigation; updating PHP remains the fix. Reading the input stream fully can prevent the demonstrated condition, but errors and shutdown paths make that unreliable as the sole mitigation. The advisory also warns against exposing PHP-FPM or LSAPI listeners to untrusted networks.
Shared sessions require checks after the update
CVE-2026-115560 concerns PHP’s session upload-progress feature, which records upload status in session data. It can write attacker-controlled data in one serialization format—the representation used to store session values—and read it in another. The mismatched reader can interpret ordinary data as serialized objects. Code execution requires suitable application classes whose behavior can be chained during deserialization, according to the session advisory.
The full advisory broadens the operational picture given in PHP’s October 23 notice. That earlier guidance described an application switching serializers at runtime and said applications that never switched could retain upload progress. November’s advisory also covers separate applications, pools, virtual hosts or command-line processes using different serializers against the same stored session. Separate PHP-FPM pools do not automatically isolate session storage. With file-based storage, both sides must access the same session ID in the same directory with suitable permissions.
The update disables session upload progress by default and blocks runtime changes to session settings while the feature is enabled. An explicit configuration can override the new default. If upload progress remains enabled, all readers and writers that can access its session data must still use the same session.serialize_handler after updating; the patch does not enforce agreement across separate configurations.
The advisory recommends isolating stores when applications need different formats, and migrating or expiring old records when changing a store’s format. Disabling upload progress must take effect before request input is processed; doing so from application code with ini_set() is too late.
A second flaw, CVE-2026-126714, affects PHP’s default file-based session handler. An interrupted replacement write can leave a mixture of old and new serialized data, enabling object deserialization on a later read. That advisory requires attacker influence over session contents, a useful interruption point and a suitable object gadget chain for code execution. Authentication requirements depend on the application’s exposed session operations.
The file-write defect dates to PHP 4.1.0 by code inspection. Disabling upload progress removes one input path but does not protect applications that independently store attacker-controlled session data. A storage backend that replaces records atomically avoids this particular defect. For the built-in file handler, the fix clears the old file before writing its replacement: an interruption can still lose data, but cannot retain the dangerous old suffix.
The PHP development team’s November 19 announcement confirms PHP 8.5.13 as a security release and urges users of that branch to upgrade. Source: PHP: News Archive - 2026.
Critical severity covers different levels of proof
The bulletin from cloud provider Amazon Web Services (AWS) lists all seven critical issues at CVSS 9.2 out of 10. That severity score is not evidence of identical exploitability. The remaining four flaws involve accessing memory after it has been freed, with different affected branches and demonstrations:
CVE-2026-129474: PHP 8.5’s fatal-error backtraces can encounter freed memory while entering magic methods used to forward calls. The advisory confirms code execution, but requires a suitable application path, memory-allocation control and usable memory addresses. Fatal-error backtraces are enabled by default in PHP 8.5, but zend.exception_ignore_args=1, supplied in php.ini-production, blocks this path. Disabling fatal-error backtraces also blocks it. PHP 8.2–8.4 have the underlying backtrace error but no established remote trigger and are outside the advisory’s affected range. The framework examples establish reachable calls, not exploitation of complete framework installations.
CVE-2026-129182: Fatal diagnostics during late shutdown can recreate stale backtrace state after PHP 8.5.12’s earlier cleanup fix. The follow-up advisory demonstrates memory corruption and worker crashes, with code execution through those specific entry points unproven. Exploitation also requires an early diagnostic in a later request on the same worker; ordinary FPM pool settings and .user.ini do not supply that trigger. PHP 8.4 and earlier lack the affected global state. Administratively disabling fatal_error_backtraces and restarting workers is the interim workaround.
CVE-2026-129481: An interrupted session shutdown can leave a reused worker with stale state. The primary advisory describes an incomplete fix for October’s CVE-2026-109619, with memory corruption and crashes demonstrated but code execution through this path unproven. PHP 8.2 is unaffected. The demonstrated configuration has OPcache disabled, but enabling OPcache alone is not a reliable mitigation because scripts can still run uncached. Disabling session upload progress does not stop this path.
CVE-2026-129496: A startup diagnostic written through PHP’s file-based error log can leave a freed timezone cache accessible to an early request diagnostic in a fresh worker. FPM’s own error log alone does not meet that condition. The timezone advisory reports remote worker crashes under ordinary request limits, alongside local command-execution demonstrations in FPM and Apache with known addresses and additional configuration assumptions. A complete independent remote bypass of address randomization has not been demonstrated. Correcting startup configuration diagnostics and restarting the master and workers, or using a logging destination such as syslog, avoids the demonstrated trigger while awaiting an update.
The wider release addresses risks beyond critical code execution. A report on the updates lists a PHP-FPM flaw that could permit local privilege escalation and a PHAR OpenSSL signature bypass, alongside information disclosure, cross-site scripting and denial-of-service fixes.
That report cites security vendor Aikido for a total of 18 CVEs. Aikido also supplies hardened PHP images with backported fixes for unsupported versions. AWS counts 17 issues across PHP 8.2–8.5, while the other release report counts seven critical and 10 high- or medium-severity flaws. The available accounts do not explain the difference; the discrepancy does not alter the fixed-version guidance.
Verify the running deployment, then decide what can remain enabled
AWS says in its security bulletin that customers running PHP on their own instances or in container images must update it themselves. Services need restarting, or images rebuilding and redeploying. Lambda has no managed PHP runtime: users of custom runtimes or images must update and redeploy their functions too. Elastic Beanstalk, AWS’s application-hosting service, delivers managed platform updates during customers’ configured maintenance windows; customers not using that option should update their environments.
At the bulletin’s publication, AWS said patched Amazon Linux 2023 packages were available in all regions, while Amazon Linux 2 and Amazon Linux 2027 Preview updates were being released. It also cautions that repository metadata does not yet list the CVE identifiers, so CVE-based filters and scanners may report fixed packages as unfixed.
AWS WAF, its web application firewall, offers limited interim coverage. Version 2.6 of the PHP Managed Rule Group adds rules for the serializer-mismatch and request-smuggling issues. They initially run in Count mode, so matching traffic is not automatically blocked. AWS recommends reviewing matches for legitimate traffic before changing the rules to Block. Coverage also depends on parsing and body-inspection limits; the rules may miss other payload variations.
AWS offers no managed rule for the other five critical issues. It says dependence on server state, application behavior and ordinary-looking requests leaves insufficient evidence for high-confidence rules. It calls patching the only complete fix and the first priority. For the interrupted-session-shutdown flaw, AWS says setting FPM’s pm.max_requests=1 and restarting workers prevents the demonstrated cross-request sequence, at a performance cost. Such measures cover individual paths rather than the whole release.
The next decision after deploying the fixes is whether session upload progress is needed. If retained, administrators must verify consistent serializers across every application and process sharing its store. They also need to check the effective configuration and version used by web workers, rather than only the command-line installation, and restart affected services.
PHP 8.2 users also face a migration deadline: the project’s archive says security support ends on December 31, 2026. For PHP 8.1 and older, third-party backports described in the reporting are a separate maintenance route; the PHP project no longer supplies regular updates for those branches.
N-able says an intruder reached a server supporting Mail Assure and SpamExperts Hosted Cloud. Mail delivery and filtering continued, but customers lost management access as the company revoked tokens and worked to restore services securely.
Microsoft is testing an optional Edge mode that blocks WebGL and WebGPU to reduce opportunities for browser exploitation. An early hands-on test found that restoring graphics for a trusted site also removed its broader Enhanced Security protections.
A critical authentication bypass gave a suspected China-linked espionage group access to VMware's virtualization control plane. Mandiant says the campaign stole signing keys and virtual-machine data, making compromise checks essential alongside patching.
TfL has shut its Oyster photocard website after a breach that may have exposed around 265,000 customers’ account details, including security answers. Existing cards still work, while the attack method and restoration timetable remain undisclosed.
Around 40 Irish credit unions are implicated in a saved-payee data breach at software supplier Wellington IT. Missing logs leave the victim count unresolved, while a minister is seeking answers about the disclosure delay.
JPMorganChase says it believes attackers accessed marketing data at outside service providers, potentially exposing customer names and email addresses. The bank says services are unaffected, but has not identified the vendors or disclosed the attack date.
Apache confirms exploitation of a Roller code-execution flaw that survives disabling XML-RPC in its administration panel. Attacks on the retired Axis 1.x library also expose enterprise applications, making product-specific mitigation and compromise checks urgent.
StepSecurity’s Elephant-led Series A will fund broader protection for developer machines, package downloads and build pipelines, alongside planned defenses for AI-agent sandboxes. Its challenge is turning open-source adoption into a larger commercial platform while proving the extra controls earn their place.
Nvidia says it has found no indication its own systems were affected after The Gentlemen ransomware group listed it on a leak site. The investigation concerns a possible incident at a partner, while the gang has supplied no public proof.
Senators from both parties plan to delay the CISA nomination of Palantir security chief Michael LoSapio after his Jan. 6 denial, adding a confirmation obstacle as the agency faces staffing losses and funding decisions.
Sean Cairncross is leaving as national cyber director, with Pentagon CIO Kirsten A. Davies reportedly selected to succeed him. The transition puts Senate confirmation at the center of a cybersecurity leadership reshuffle.
Windows baseline protection combines existing PC safeguards into a verifiable pass-or-fail result. Microsoft defines the standard; developers choose whether failure means a warning, fewer features or blocked access.
F5 lists fixed releases for a critical nginx HTTP/2 flaw, while the wider NGINX2Root disclosure covers five independent nginx attack paths and a separate Linux kernel bug. Remediation depends on configuration, supplier patch levels and replacing vulnerable running processes.
Tyler Robert Buchanan received six years in U.S. prison for a phishing and SIM-swapping conspiracy that stole at least $11.6 million from individuals. He is the last of five defendants sentenced; restitution remains pending.
The new Threat Disruption Center makes TRM Labs its main technology partner following a reported $94.66 million sole-source award for Homeland Security Task Force investigations. A rival lost its court challenge, but the launch leaves the center’s share of that spending and its performance benchmarks undisclosed.
Fandango says payment details from certain October 8–11 transactions may have been exposed. State disclosures provide only a partial affected count, while the company has not explained how the checkout page was compromised.
Norway’s state-controlled oil and gas group is working to neutralise an attack on some IT systems. Employee services may be disrupted, but Equinor says operations and production remain unaffected and it has found no indications of data theft.
Tor urges relay operators to install 0.4.9.17 as a continuing DDoS attack strains its privacy network. A post-upgrade operator account describes further disruption, while Bitcoin connectivity measurements show partial recovery with important limits.
Malicious code in Optimizely website-testing projects could swap cryptocurrency addresses and skim payment cards. Optimizely says it has fixed the vulnerability and removed the code, but visitor exposure and losses remain unquantified.