PHP 8.5.12 - Security Release for Two Remote Code Execution CVEs


PHP 8.5.12 is a security release for the PHP 8.5 branch, with tag php-8.5.12, published on October 21, 2026. It fixes two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which can allow unauthenticated remote code execution. If you run PHP 8.5 anywhere in a web processing or CMS pipeline, this is a patch now release.

The full release notes and downloads are on the GitHub release page.

The notes are short. They state three things.

  • Two critical vulnerabilities are fixed.
  • Both can lead to unauthenticated remote code execution.
  • There are no complete mitigations. Updating is the only safe choice.

The release page does not describe the affected extensions, the code paths, or the trigger conditions. That detail lives in the security advisory linked from the notes. The notes also point to the ChangeLog for the list of changes. Read both before you decide how fast to move. This post does not guess at anything beyond what the notes state.

Most security releases come with a stopgap. You disable an extension, tighten an ini setting, or put a rule in front of the service. The notes say none of that is complete here.

For operators, that changes the plan in a few ways.

  • A WAF rule or a config toggle cannot be your closing action. At best it buys time.
  • Unauthenticated means network reachability is the main gate. Anything that accepts requests from the internet is first in line.
  • Remote code execution on a PHP host usually means access to whatever that process can read. That includes environment variables, mounted secrets, database credentials, and queue connections.

For data engineering teams, the last point is the one that hurts. PHP often sits at the edge of an ingestion path: a CMS that feeds a warehouse, a webhook receiver, a small admin tool with a database login. Those hosts tend to hold credentials with broad read access. Treat them as high value even if the PHP code itself is small.

Before patching, build the list. The release only covers the 8.5 line, so start there.

  • Check every image and host for the PHP version. php -v on the host, or the base image tag in your Dockerfiles.
  • Look at CLI workers and cron jobs as well as web SAPIs. A queue consumer written in PHP runs the same interpreter.
  • Check vendor images that bundle PHP. Your own pin may be fine while a third party image lags behind.
  • Confirm whether you build from source or use distribution packages. Source users get the tarball from the downloads page. Windows source and binaries are on the Windows downloads page.

Distribution packages may arrive on their own schedule. If you rely on one, check when it picks up 8.5.12 rather than assuming.

The notes say to update immediately. A sensible order inside that constraint:

  1. Internet facing web hosts and containers first.
  2. Webhook receivers and API endpoints that accept unauthenticated input.
  3. Internal web tools and admin panels.
  4. CLI workers and scheduled jobs.

Rebuild images instead of patching running containers. Then verify with php -v in the deployed pod or host, not just in the build log. A rolled out tag that still points at an older cached layer is a common way to think you are patched when you are not.

After the update, review access logs and process behavior for the period before you patched. The notes give no indicators of compromise, so the advisory is the place to look for specifics. If the advisory has none, check for unexpected child processes from your PHP workers and outbound connections that do not match normal traffic.

This is a patch release inside the 8.5 line. The release notes do not list breaking changes or migration steps. The ChangeLog is the authoritative list of what else changed, so skim it for anything that touches extensions you depend on, then run your usual test suite before the production roll.

If you are on an older branch, the release notes do not say whether those branches are affected. Check the advisory for that answer instead of assuming either way.