[Project] I translated the full PHP 8.4.26 HTTP-only RCE research repository into English, including technical documentation and code comments
Description
This research project documents a remote code execution (RCE) vulnerability in PHP version 8.4.26 under the official production configuration. The exploit chain uses only HTTP requests and includes an ASLR bypass via out-of-bounds memory disclosure. It does not require enabling display_errors or modifying the default 128 MB memory limit. The attack involves multi-stage exploitation including PHP session-state corruption, heap manipulation, and control-flow hijacking. The exploit was successfully reproduced on an Apache prefork configuration with a 10/10 success rate in the tested environment. The repository provides detailed technical documentation, code comments, and evidence of the exploit's effectiveness. The translation effort makes the original Chinese research accessible to the international security community.
Reddit Discussion
I recently came across 9bie's php2shell research, which demonstrates an HTTP-only RCE exploit chain against PHP 8.4.26, including an ASLR bypass, under the official production configuration.
While the original repository already provides an English README, much of the detailed research documentation and code commentary is written in Chinese.
To make the research more accessible to the international security community, I put together an English-translated version of the repository, covering the technical documentation and code comments while preserving the original implementation and project structure.
For context, the original research demonstrates:
- Remote code execution using HTTP requests only.
- An ASLR bypass using out-of-bounds memory disclosure.
- Exploitation without enabling
display_errorsor modifying the default 128 MB memory limit. - A multi-stage exploitation chain involving PHP session-state corruption, heap manipulation, and control-flow hijacking.
- Successful reproduction under the official Apache prefork configuration, with a reported 10/10 success rate in the tested environment.
The repository also contains extensive technical notes covering the development of the exploit, intermediate findings, failed approaches, memory-layout analysis, and reproduction evidence.
English-translated repository:
https://github.com/yanoshercohen/php2shell-bypass-aslr-exp-en
Original project by 9bie:
https://github.com/9bie/php2shell-bypass-aslr-exp
All credit for the vulnerability research and exploit development belongs to the original author. My contribution is making the existing research materials and code commentary accessible in English.
Sharing this for anyone who wants to explore the research beyond the README.
Links cited in this discussion
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The project translates and documents a complex HTTP-only remote code execution exploit against PHP 8.4.26. The exploit chain bypasses ASLR by leveraging out-of-bounds memory reads and uses PHP session-state corruption and heap manipulation to hijack control flow, ultimately achieving code execution without requiring display_errors to be enabled or memory limits to be changed. The exploit works on the official PHP production configuration and Apache prefork MPM with MaxRequestWorkers=150. It involves pinning workers, chunked multipart requests to bypass post_max_size, and precise memory layout manipulations. The research includes extensive technical notes, failed attempts, memory layout analysis, and reproducible proof-of-concept code. The translation effort aims to make this detailed research accessible to English-speaking security professionals.
Potential Impact
Successful exploitation results in remote code execution on servers running PHP 8.4.26 with default production settings, including display_errors=Off and memory_limit=128M. This allows an attacker to execute arbitrary system commands remotely via crafted HTTP requests without requiring any configuration changes or enabling debugging features. The exploit has been demonstrated with a 10/10 success rate in tested environments, indicating high reliability under the specified conditions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, consider monitoring vendor communications for updates. No vendor advisory or patch information is provided in the source data. The exploit requires no configuration changes to enable, so mitigation through configuration alone may be insufficient.
Technical Details
- Source Type
- Subreddit
- cybersecurity
- Reddit Score
- 0
- Discussion Level
- minimal
- Content Source
- reddit_link_post
- Post Type
- link
- Newsworthiness Assessment
- {"score":30,"reasons":["external_link","newsworthy_keywords:rce","established_author","very_recent"],"isNewsworthy":true,"foundNewsworthy":["rce"]}
- Has External Source
- true
- Trusted Domain
- false
Threat ID: 6ada83ec4d27ba8daa7f4f1c
Added to database: 10/22/2026, 21:45:16 UTC
Last enriched: 10/22/2026, 21:45:21 UTC
Last updated: 10/23/2026, 05:15:15 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.