Back Sploitus Exploit for Improperly Controlled Sequential Memory Allocation in Php
A loopback-only Docker lab for studying CVE-2026-109618 with an Onda Living PHP storefront. The website uses the same source files in a vulnerable and a patched PHP container. A separate debug container supports the local, white-box RCE demonstration.
├── compose.yaml # PHP 8.4.26 and 8.4.27 comparison
├── exp.py # Local lab driver and shell interface
├── probe_reclaim.py # Loopback HTTP request generator
├── gdb-calibrate.py # Local debugger calibration
├── relay.php # Local shell relay
- Docker Desktop or Docker Engine with Compose v2
Open ` for PHP 8.4.26 or ` for the patched PHP 8.4.27 comparison. Both serve `website/` read-only.
The driver builds and starts its pinned PHP 8.2.6 debug container automatically. It calibrates addresses with GDB, sends the local test request, verifies execution as `www-data`, then restores the storefront at `
For the interactive local shell, run `python .\exploit\exp.py`. Commands appear under a `current/path >` prompt; enter `exit` to finish. For the file-based proof, run `python .\exploit\exp.py --proof`. Results are written to `exploit/evidence/`, which is excluded from Git.
docker compose -f .\exploit\compose.yaml down
This is a controlled, localhost-only reproduction. `exp.py` takes no remote target and relies on local GDB and process mappings for address calibration. It does not demonstrate an HTTP ASLR leak or a general exploit against arbitrary PHP installations. The PHP 8.4.26/8.4.27 pair is for patch comparison; the RCE demonstration was verified in the pinned PHP 8.2.6 debug environment.
The reproduction is adapted from [lzz0403's local CVE-2026-109618 PoC]( See the [official PHP advisory]( for affected versions and remediation.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
