Oriel — AI & technology worth noticing, every day.

PHP2Shell: Your Code Was Fine, The Engine Was Not

Post · https://dev.to/lovestaco/php2shell-your-code-was-fine-the-engine-was-not-gc2

Hello, I'm Maneshwar, and I'm building LiveReview — a blast-radius aware AI code review built for...

First seen by Oriel on .

AI summary

The article explains two critical PHP engine vulnerabilities, PHP2Shell, that can enable unauthenticated remote code execution when request startup or cleanup leaves invalid memory state.

  • CVE-2026-109618 can trigger memory corruption when an out-of-memory failure interrupts request startup and cleanup handles partially initialized state.
  • CVE-2026-109619 is a use-after-free in worker-level state that can persist after fatal errors and be read by a later request.
  • The article says mod_php is at highest risk for the startup bug; public proof-of-concept exploits are currently limited to particular operating systems, PHP versions, and web servers.
  • Fixed releases are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35; operators should restart or reload workers after upgrading.
  • Temporary mitigations include disabling session upload progress and, on PHP 8.5, fatal error backtraces, but the article emphasizes that these do not replace patching.

#php #memory safety #remote code execution #web security

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Reactions

Total public reactions reported by the source; distinct from points and likes.

  • DEV Community: 26, latest observation ; +9 over observed period since

Comments

Comment count reported by the source.

  • DEV Community: 5, latest observation ; +3 over observed period since

Aliases

SourceExternal IDURL
DEV Community4899612https://dev.to/lovestaco/php2shell-your-code-was-fine-the-engine-was-not-gc2 Read discussion