Release advisory
PHP project
Emergency PHP releases and the original security advisory.
47 FIRST-PARTY PUBLICATIONS
Original statements from researchers, maintainers, hosting providers and public agencies.
The maintainers, researchers and providers responding to PHP2Shell.
Release advisory
Emergency PHP releases and the original security advisory.
Original research
Original research into the PHP runtime flaws and attack paths.
Coordinated disclosure
Coordinated disclosure with PHP maintainers, researchers and providers.
Protection update
WAF response, observed attack traffic and PHP patching guidance.
Platform response
Cloud, Forge and Vapor instructions for the PHP security release.

Service notice
Announced partial website downtime ahead of the PHP disclosure.

Service notice
Announced a precautionary website and API shutdown pending a fix.

Project advisory
The Drupal Security Team’s own PHP security announcement.
Research & advisory
An alert on PHP2Shell and coordinated patch preparations.

Distribution update
Backported PHP fixes and updated AlmaLinux packages.

Hosting response
A protection update for its hosting platforms and PHP guidance.
Research & advisory
An exposure assessment and PHP vulnerability alert.
Distribution update
Canonical’s PHP package fixes for supported Ubuntu releases.
Research & advisory
PHP update guidance and Snort detection coverage.

Detection release
Open-source Zeek and Suricata detections for defenders.
Research & advisory
Detection and visibility guidance for the PHP vulnerabilities.
Hosting response
A dated hosting response update on PHP2Shell protections.
Research & advisory
Guidance to find affected PHP deployments and update.
Research & advisory
Early guidance on inventory, patch preparation and monitoring.
Research & advisory
Analysis of the PHP flaws and defensive guidance.

Hosting response
A first-party notice of precautionary service shutdowns.

Hosting response
A hosting status notice on deploying patched PHP versions.
Research & advisory
Unit 42 threat assessment and patching recommendations.
Research & advisory
A runtime security alert for PHP website operators.
Research & advisory
Why the fix belongs at the PHP runtime and hosting layer.
Research & advisory
Why PHP inventory and clear patch ownership matter.
Research & advisory
A technical FAQ covering the emergency PHP release.
Maintainer response
How PHP’s maintainers coordinated fixes and the emergency release.
Research & advisory
A threat alert distinguishing verified facts from exploit claims.
Research & advisory
Research updates, reproduction and PHP patch guidance.
Research & advisory
A research overview of the flaws and emergency update schedule.
Official security notices from national and public-sector organizations.

Government alert
Calls for immediate PHP patching and taking affected systems offline when they cannot be updated.

Federal warning
Urges immediate PHP updates or taking unmitigated systems offline.

Government warning
Urges PHP updates or taking unmitigated systems offline.
Government advisory
Security Advisory 2026-018: critical PHP vulnerabilities.
Government advisory
Urgent Dutch guidance on the two critical PHP flaws.
Government alert
Calls for immediate updates and mitigation of PHP systems.

Government warning
Czech national warning about both critical PHP2Shell flaws.

Government alert
Australia’s alert on critical PHP vulnerabilities.
Government warning
Urged security updates for critical PHP vulnerabilities.

Government bulletin
Security bulletin AV26-1070 on PHP updates.
Government warning
Warning 196/2026 on PHP remote code execution.
Government alert
France’s national alert on multiple PHP vulnerabilities.
Public statement
Announced two websites taken offline as a precaution.

Government alert
High-threat security alert A26-10-36.
Government notice
Notice to prepare for PHP’s critical security release.

Public-sector alert
Cyber Alert CC-4875 on the PHP2Shell vulnerabilities.
No matching organizations. Try another name or choose all sources.
Publications dated 20–21 October 2026; some describe the situation before patches were released. Logos identify the cited sources; no endorsement or affiliation is implied. Source data · Logo credits
Start with the inventory
Open your codebase, copy the brief and review the migration plan.