Why PHP's Recent Critical RCEs Are an Architectural Non-Problem in Elixir
![]()
Two unauthenticated remote code execution bugs in PHP 8.2 to 8.5, disclosed in October 2026 and rated 9.2 under CVSS v4.0, prompt this argument for the BEAM. CVE-2026-109618 is an out-of-memory failure during request start-up that leaves data half-built for PHP's cleanup to misread as valid pointers; CVE-2026-109619 is a use-after-free in which a reused worker hands stale request data to a later request. Neither can happen in Elixir, the author argues, because each request runs in its own process with a private heap, a failed allocation kills only that process, and nothing mutable is shared or carried between requests. The concessions are fair ones: a runaway process can still starve the machine, so set :max_heap_size, and a smaller ecosystem still carries supply-chain risk, so run mix hex.audit and Sobelow in CI.
Was this useful?