CVE-2026-109618 - log back

CVE-2026-109618 edited at 21 Oct 2026 17:04:13
References
+ https://www.php.net/archive/2026.php#2026-10-21-4
https://www.php.net/archive/2026.php#2026-10-21-5
- https://www.php.net/archive/2026.php#2026-10-21-4
https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w
CVE-2026-109618 edited at 21 Oct 2026 17:03:25
References
https://www.php.net/archive/2026.php#2026-10-21-5
+ https://www.php.net/archive/2026.php#2026-10-21-4
https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w
CVE-2026-109618 edited at 21 Oct 2026 16:52:52
References
+ https://www.php.net/archive/2026.php#2026-10-21-5
https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w
CVE-2026-109618 created at 21 Oct 2026 14:08:45
Severity
+ Critical
Remote
+ Remote
Type
+ Arbitrary code execution
Description
+ PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. In some contexts, request memory is temporarily reachable before it is fully initialized. If any allocation fails at that point, PHP does not properly account for the early exit and leaves the request memory in an invalid state. The failed allocation does not need to be related to the invalid memory. The request shutdown procedure may then read or branch on it. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
References
+ https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w
Notes