
PHP2Shell: The Emerging Cyber Threat Targeting PHP Infrastructure Worldwide
Executive Summary
The PHP ecosystem is facing one of its most significant security crises in recent years. Two critical vulnerabilities, collectively known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), have exposed millions of internet-facing PHP deployments to unauthenticated remote code execution (RCE). What began as vulnerability disclosure rapidly evolved into widespread scanning, exploitation attempts, and highly targeted threat actor activity.
Recent intelligence suggests that a suspected North Korean (DPRK)-linked threat operation has moved beyond reconnaissance into active scanning of vulnerable PHP infrastructure, while security researchers have already demonstrated successful exploitation against popular platforms such as WordPress, Drupal, and Joomla.
Organizations running PHP-based applications should treat this threat as Critical and prioritize immediate remediation.
Inside PHP2Shell
PHP2Shell refers to two critical vulnerabilities affecting the PHP runtime itself rather than any individual application built on PHP.

Vulnerabilities
CVE-2026-109618 : Out-of-memory corruption vulnerability
CVE-2026-109619 : Stale global state use-after-free vulnerability
For additional details, refer to : https://portal.cyberxtron.com/vulnerability-intelligence/cves
Unlike application-specific flaws, these vulnerabilities impact the core PHP engine powering:
- WordPress
- Drupal
- Joomla
- MediaWiki
- Magento
- Laravel applications
- Custom PHP applications
The vulnerabilities allow attackers to execute code before application logic is reached, making traditional application-level security controls less effective.
PHP2Shell: Understanding the Impact
PHP powers a massive portion of the internet.
Researchers described PHP2Shell as potentially comparable to landmark vulnerabilities such as:
- Heartbleed
- Log4Shell
The reason is simple:
Attackers do not need:The vulnerabilities exist in PHP itself
- WordPress vulnerabilities
- Plugin vulnerabilities
- Authentication credentials
- Misconfigured applications
The Technical Root Cause
Both vulnerabilities stem from PHP's handling of request failures.
When PHP encounters situations such as:
- Out-of-memory conditions
- Fatal errors
- Request aborts
- Timeout events
It may leave internal memory structures in an inconsistent state.
A subsequent request handled by the same worker process can unexpectedly inherit that maliciously influenced state, resulting in:
- Memory disclosure
- Use-after-free conditions
- Memory corruption
- Remote code execution
This cross-request contamination mechanism enables attackers to move from simple error conditions to complete server compromise.
AI's Role in Discovering PHP2Shell
One of the most remarkable aspects of PHP2Shell is how it was discovered.
Security researchers reported using advanced AI systems to identify, analyze, and validate exploitation paths.
Traditionally, memory corruption vulnerabilities in complex software require:
- Months of expert analysis
- Advanced reverse engineering
- Extensive debugging
Research teams noted that frontier AI models significantly reduced the time needed to:
- Discover vulnerable code paths
- Analyze memory corruption behavior
- Generate exploit hypotheses
- Validate mitigation strategies
This incident may represent an important shift in cybersecurity where AI accelerates both vulnerability discovery and defensive research.
Threat Landscape Evolution
Phase 1: Disclosure
October 2026 saw emergency disclosure and patch releases for PHP2Shell vulnerabilities.
Researchers warned that public exploit code would likely emerge quickly.
Phase 2: Global Scanning
Within days:
- Internet-wide scanning activity increased dramatically.
- Vulnerable PHP systems were identified globally.
- Exploit attempts appeared before many organizations patched.
Phase 3: Targeted Campaign Activity
Threat intelligence reported that operators speaking Korean were allegedly coordinating activities against vulnerable PHP assets.
Intelligence indicated focus areas including:
Geographic Targets
- United States
- Japan
- South Korea
- Taiwan
- Singapore
- India
- Thailand
- Indonesia
- Australia
- UAE
- Saudi Arabia
- European Union
Industry Targets
Tier 1:
- Government agencies
- Financial institutions
- Banks
Tier 2:
- Manufacturing
- Logistics
- Aviation
- Transportation
Tier 3:
- Online trading platforms
- Construction firms
- Transaction platforms
The campaign reportedly shifted from reconnaissance to low-volume deliberate scanning of carefully selected targets.
Affected PHP Versions
Fixed Versions
Organizations should update to at least:
|
PHP Branch |
Secure Version |
|
PHP 8.5 |
8.5.12+ |
|
PHP 8.4 |
8.4.27+ |
|
PHP 8.3 |
8.3.36+ |
|
PHP 8.2 |
8.2.35+ |
End-of-Life Versions :The following versions present significant risk:
- PHP 8.1
- PHP 8.0
- PHP 7.x
- PHP 5.x
Many of these branches no longer receive official security updates and should be upgraded or isolated immediately.
Additional PHP Security Issue: Brotli RCE Risk
While organizations were still responding to PHP2Shell, another security issue emerged.
PHP released updated Windows packages to address:
vulnerability :CVE-2026-111497
This vulnerability affects the Brotli compression library bundled with PHP Windows distributions.
Potential impact includes:
- Memory corruption
- Code execution
Affected Windows builds were rebuilt as:
- 8.5.12-1
- 8.4.27-1
- 8.3.36-1
- 8.2.35-1
Organizations running PHP on Windows should ensure they are using the updated "-1" package builds.
Detection Opportunities
Security teams should investigate:
Web Activity
- Suspicious multipart/form-data requests
- Large upload requests
- Unexpected upload-progress parameters
- PHP_SESSION_UPLOAD_PROGRESS anomalies
Application Behavior
- Frequent HTTP 500 errors
- PHP worker crashes
- Memory exhaustion events
- Unexpected process restarts
Immediate Mitigation Checklist
Priority 1 - Immediate
✅ Patch PHP to supported fixed versions
✅ Restart all PHP workers and services
✅ Restart Apache, Nginx, PHP-FPM, and mod_php processes
✅ Verify the running PHP version, not just CLI version
✅ Inventory all internet-facing PHP installations
Priority 2 - Within 72 Hours
✅ Review logs back to October 17, 2026
✅ Search for:
- OOM events
- Worker crashes
- Multipart anomalies
- Unexpected child processes
✅ Hunt for web shells
✅ Monitor for suspicious outbound connections
Priority 3 - Strategic
✅ Remove unsupported PHP versions
✅ Implement WAF protections
✅ Restrict direct origin access
✅ Improve runtime monitoring
✅ Deploy process-execution detection
✅ Strengthen asset inventory capabilities
Indicator Of Compromise (IOC’s)
Hash:
0c5486f06620e26e316f4b33f318b0d646d5e1133789331aa2fed012360d1486
IP:
146.70.114[.]180,
146.70.114[.]182,
147.175.149[.]67,
147.78.168[.]57,
109.56.219[.]150,
158.173.75[.]178,
185.203.18[.]54,
185.235.212[.]105,
103.77.210[.]80,
128.90.176[.]13,
138.199.34[.]201,
145.255.150[.]25,
149.102.232[.]44,
149.102.232[.]93,
158.173.242[.]133,
147.78.168[.]67,
102.207.250[.]188,
94.154.43[.]185,
75.119.143[.]189,
117.203.73[.]63,
146.190.107[.]103,
95.217.164[.]124,
124.122.142[.]142,
188.80.228[.]122,
134.209.181[.]133,
134.209.252[.]157,
119.63.72[.]54,
138.68.161[.]170,
95.216.5[.]90,
103.21.161[.]105,
115.96.27[.]126,
185.207.232[.]121,
78.47.85[.]99,
92.118.112[.]100,
103.216.220[.]92
URL:
hxxp://92.118.112[.]100/nfs
Conclusion
PHP2Shell represents one of the most impactful web infrastructure vulnerabilities disclosed in 2026. The combination of critical unauthenticated RCE flaws, active exploitation, targeted campaign activity, and AI-assisted vulnerability research has created a perfect storm for defenders.
Organizations running PHP-powered applications should assume that attackers are actively searching for vulnerable systems and prioritize remediation immediately. With successful exploitation already demonstrated and multiple threat actors showing interest, the window for preventive action is rapidly closing.