Archive

News on 23 Oct 2026

Calendar: October 2026

Published this day

Updated this day

  • Act nowVulnerabilitiesUpdated

    Critical PHP flaws: update now

    PHP released fixes on 21 Oct 2026 for two critical bugs that can allow remote code execution without a login. Here is who is affected and what to do.

    The flaws may also expose secrets. SecurityWeek reports that the two flaws can also be used to read sensitive memory of the PHP process, and that memory may hold credentials, API keys and other secrets. PHP's maintainers say every PHP setup that handles web requests is potentially at risk (PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed), and the flaws reach back to nearly all releases, to PHP 5.4. Several security firms (Amazon, Hadrian, Patchstack, Cloudflare and Vega, which saw a public proof of concept in use) report exploitation attempts, mostly through PHP's session upload-progress path, and watchTowr says none of the attempts it saw had succeeded. Governments are urging immediate patching. Our precaution, not a confirmed case: **after you update, consider rotating the database passwords and API keys stored on any server that ran an affected PHP and faced the internet.** Updating PHP is still the real fix.

  • Act nowVulnerabilitiesUpdated

    Critical PHP flaws: update now

    PHP released fixes on 21 Oct 2026 for two critical bugs that can allow remote code execution without a login. Here is who is affected and what to do.

    A third PHP issue, CVE-2026-115560, is unpatched but unlikely to affect you. PHP.net published an informational advisory today: the risk exists only if an app sets `session.serialize_handler` to `php_binary` or `php_serialize` and then switches it to `php` at runtime with `ini_set()` before `session_start()`, with session upload progress still enabled. The fix will come in the regular release, with a full advisory then. **Keep the 21 Oct updates as your main action.** As an extra step, set `session.upload_progress.enabled=0` until the next bugfix release. If you already did that for CVE-2026-109619, you are covered. Apps that never change the serialize handler at runtime can leave it enabled.

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks