Application Security

PHP Security Update: Patch and Verify

Use the package maintainer’s advisory, update every serving instance, verify the running runtime and retain evidence. A change ticket alone does not prove production is fixed.

Bravewall brand mark for this editorial article.
In this article 6 sections
ShareLinkedInWhatsAppEmail

Confirm the fix for your package

Start with the PHP project advisory and the operating-system or hosting vendor that supplies the runtime. The PHP project listed PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 as fixed upstream releases for CVE-2026-109618 and CVE-2026-109619. Distributions and long-term-support vendors may apply the security fix while keeping a different package number; follow the security notice for your exact package. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026

PHP 8.1 and older no longer receive fixes from the PHP project. Some vendors may maintain their own patched packages. Verify that support and patch status directly; where an applicable supported package is unavailable, plan a controlled upgrade to a supported branch. PHP 2026 news archive: supported branches and security releases

Plan and apply the change

  • Identify all production instances, pools, containers and workers using the affected runtime.
  • Confirm the vendor package and its security status; record the advisory and package source.
  • Use the organisation’s normal change process to assess compatibility, schedule the update and prepare an appropriate rollback or recovery approach.
  • Apply the package update to each relevant environment and restart or recycle processes where the vendor requires it.
  • Check that load balancers, autoscaling groups and failover nodes will not reintroduce an older image or package.

The PHP project’s listed temporary mitigations address specific paths and do not make an installation safe. Use them only with the current advisory and a qualified administrator; do not copy settings from a general article into production without understanding application impact. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026

Verify the running state

After deployment, verify the package actually loaded by the production runtime—not only the package installed on one host. Check each serving node, container image or managed service through its appropriate administrative evidence. Confirm that old workers have exited if required, and that deployments, failover and rollback images point to the corrected package.

Record the asset, package/vendor version, source advisory, deployment time, verification method, instances checked, owner and any exceptions. If the provider says the fix is included in an older package, retain its release note or confirmation. Recheck after routine deployment or autoscaling changes so the fix remains in place.

Separate patching from incident investigation

A successful update establishes the current package state; it does not establish whether the system was accessed before the update. If there are indicators of compromise, preserve relevant logs and evidence and follow the organisation’s incident process. Determine applicable reporting duties with the responsible compliance owner.

Plan for branch support

PHP 8.2 is scheduled to reach end of security support on 31 December 2026. Teams using it should address the current security update and plan a supported-version transition with application testing and operational ownership. Do not leave an upgrade plan as an unowned note in the patch ticket. PHP 2026 news archive: supported branches and security releases

Sources and further guidance

Regulatory applicability depends on the organisation and the provisions in force. Check the linked primary sources before acting.

Related reading and capabilities

Frequently asked questions

Does installing the update on one server complete the fix?

Only if that server is the complete serving environment. Check pools, workers, containers, failover and autoscaling images that can still handle requests.

Can I rely on a provider fix if the package version looks old?

Yes, if the provider documents that the relevant fix is included in your exact package. Keep the provider notice or other authoritative evidence.