Zarro Technology · Security briefing

Today’s briefing covers fresh runtime and website fixes. PHP’s 19 November session-handler advisory raises the required patch level again, while Drupal’s 18 November notice addresses installer-related takeover under specific conditions.

1. PHP: interrupted session writes can enable code execution (Critical)

CVE-2026-126714 (9.2)

Impact

PHP’s default file-based session handler can retain mixed session data after an interrupted write. With attacker-controlled session contents, a suitable interruption and an application object gadget chain, this can execute code as the PHP worker. Authentication requirements depend on the application. The advisory does not establish active exploitation.

Remediation

Update affected PHP branches to 8.2.36, 8.3.37, 8.4.28 or 8.5.13, or a vendor-confirmed backport. Earlier emergency releases are below these new fixed levels. Include PHP-FPM, Apache modules and container images; restart or replace affected workers using the supported procedure.

As a temporary measure, PHP recommends disabling unneeded upload progress administratively and limiting untrusted session data. This setting removes one input path, not the underlying defect:

session.upload_progress.enabled=0

Checks and IoCs

Verify the runtime and session handler actually used by web requests. Review unexplained session corruption, worker crashes and unexpected PHP child processes as hunting leads. No campaign-specific IoCs are published; their absence cannot establish that a server is clean.

Sources: PHP — prerequisites, fixed releases and mitigation · PHP — release changelog

2. Drupal: installer can enable site takeover (Critical)

CVE-2026-132165

Impact

Drupal’s SA-CORE-2026-017 warns that an attacker can attempt reinstallation under specific conditions, potentially taking over a site or executing code. The advisory’s Critical rating uses Drupal’s own risk scale; no numeric CVSS score is asserted. It identifies proof-level exploitability but does not report confirmed attacks in the wild.

Checks and remediation

Update Drupal 10.6.x to 10.6.22, 11.3.x to 11.3.22 or 11.4.x to 11.4.13. Older unsupported branches require migration. Follow Drupal’s installer-hardening guidance as well: preventing the web server from writing to or changing permissions on settings.php mitigates some exploit paths.

Check installer exposure, unexpected settings changes and new privileged accounts. These are investigation leads, not campaign-specific IoCs. Drupal Steward protection covers known vectors, but the vendor still recommends upgrading in case additional paths are discovered.

Sources: Drupal — affected versions, fixes and installer-hardening guidance

Zarro Technology