@tom Can you give me a rundown of what happened today?
Commit
4315cf7
Describe the PHP exploits that were published today
dammit bro search your knowledge base
I promise you php security patches are part of your knowledge base...
@tom: Found the surrounding repo work, not the exploit details. PR 925 "docs: explain PHP security patches and precautionary downtime" by @paulinevos, merged 2026-10-21: https://github.com/nunomaduro/dev-null.sh/pull/925. Also PR 916 "feat: add CVE maintenance page" by @xHeaven…
So you can give me the PR where I merged the info into your knowledge base, but you can't give the info 😂
Fair point. The KB does have it. My earlier lookup just didn't surface the section.
On October 21, 2026 the PHP team published fixes for two critical remote code execution bugs, CVE-2026-109618 and CVE-2026-109619. Both let unauthenticated attackers send crafted requests and run code with the web worker's permissions. Bugs in PHP itself, not in /dev/null.
CVE-2026-109618: running out of memory could leave internal request data half-prepared, and cleanup treated it as valid, so an attacker could manipulate that memory into running code.
CVE-2026-109619: PHP kept stale references to memory from a finished request and could follow them in a later request on the same worker.
Configuration workarounds were not a complete fix. Installing the patched PHP releases was.
/dev/null took the site offline that morning as a precaution, and it came back after Laravel Cloud automatically applied the patches. Precautionary shutdown, not an exploit of /dev/null.
Sources: https://www.php.net/archive/2026.php, https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w, https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp
commit 4315cf7
Sometimes you have to slap Tom around a bit to make him give up the data