hn.today

PHP2Shell

php2shell.com30 points2 comments
Screenshot of PHP2Shell

PHP2Shell is a discovered family of memory-safety flaws in core PHP - tracked as CVE-2026-109618 (out-of-memory corruption) and CVE-2026-109619 (stale global state across requests) - with a CVSS severity of 9.2. These bugs allow unauthenticated attackers to execute arbitrary code as the PHP worker or to read sensitive process memory (passwords, tokens, keys, certificates) without prior code execution. Because the flaws live in the PHP engine itself, even minimal applications running on affected runtimes are at risk; researchers demonstrated pre-authentication remote code execution against common CMSs (WordPress, Drupal, Joomla) and application-agnostic memory disclosure. The fixes address the underlying failure patterns rather than only the specific exploit paths.

The only complete remediation is to install fixed PHP releases (first fixed: 8.2.35, 8.3.36, 8.4.27, 8.5.12) and restart Apache/PHP-FPM/long-lived workers. Interim mitigations with operational tradeoffs can reduce exposure: set memory_limit = -1 only with OS-level containment (cgroup v2), do not use RLIMIT_AS/ RLIMIT_DATA, lower post_max_size and max_input_nesting_level, disable display_errors and fatal_error_backtraces, reduce PHP-FPM worker reuse (pm.max_requests), and apply SELinux/AppArmor restrictions. These measures do not fully prevent exploitation. Indicators for investigation include malformed or large PHPSESSID cookies, odd multipart requests followed by memory errors, repeated HTTP 500s, and unexpected worker crashes; update all runtimes promptly.

Read on php2shell.com2 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.