NSA and NCSC Tell Unpatched PHP Servers to Go Offline
By @sharedot · · 8 pages
- Cybersecurity
- Php2shell
- Vulnerability Patching
NSA and UK NCSC issued urgent advisories on the PHP2Shell flaws, urging organizations to patch immediately or take affected PHP servers offline.
What Happened
On October 21, 2026, PHP released emergency security updates fixing two critical memory-safety vulnerabilities, CVE-2026-109618 and CVE-2026-109619, collectively nicknamed "PHP2Shell." The fixes landed in PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35.
Both flaws carry a CVSS score of 9.2 and can allow unauthenticated attackers to execute code on any web server running an affected PHP version, independent of the application's own security.
Why Governments Moved So Fast
The NSA issued a formal advisory on October 21 urging US government departments and agencies to patch immediately, warning that PHP2Shell could let attackers seize affected web servers without prior access or authentication to steal data, disrupt services, or move deeper into networks.
The UK's NCSC separately encouraged organizations to take immediate action, and CERT-EU and the Australian Cyber Security Centre also pushed urgent patching guidance.
The 'Go Offline' Precedent
Both the NSA and the NCSC gave the same stark fallback: organizations that cannot immediately patch or mitigate should take affected PHP systems offline until fully remediated.
The NCSC adds that if a system cannot be updated or disabled right away, operators should assess it for evidence of compromise and look for backdoors before upgrading. Per Reuters, the disclosure prompted several European government websites to go dark temporarily as operators applied fixes.
Who Is Exposed
The NCSC states that every version of PHP may be affected, so organizations should not limit discovery to outdated installs but inventory PHP generally, prioritizing internet-facing systems.
PHP powers roughly 70% of websites, and Wiz Research demonstrated unauthenticated remote code execution against the latest images of WordPress, Drupal, and Joomla, plus disclosure of process memory containing passwords, tokens, and API keys.
The NCSC-NL published an inventory list of PHP-dependent products.
The Temporary Mitigations
For operators who cannot patch yet, the PHP project recommends setting memory_limit to -1 to address CVE-2026-109618, and disabling session.upload_progress.enabled and fatal_error_backtraces to mitigate CVE-2026-109619. PHP cautions that configuration changes offer only partial protection.
Cloudflare deployed WAF rules for PHP2Shell about nine hours before public disclosure, enabled by default on all plans, but reports attackers are already mutating payloads to evade the rules, so patching remains essential.
What Comes Next
The NSA says it will keep working across the intelligence community, including CISA, to identify and address affected systems. The NCSC will continue monitoring for impact on UK organizations and points operators to its Early Warning service and assured Cyber Incident Response providers.
The NSA also advises enhanced logging and replacing end-of-life PHP services that cannot take the patch. Because PHP often arrives through base images and hosting providers, remediation may require rebuilding containers rather than updating a CMS alone.
Sources
- ncsc.gov.uk › Critical security issue affecting PHP
- forkast.news › AI-Assisted Research Uncovers Critical PHP2Shell RCE Vulnerabilities
- nsa.gov › NSA Advisory: Critical Patches Recommended for PHP Vulnerabilities
- cnn.com › Global websites shut down after AI found a critical flaw affecting 70% of the internet
- wiz.io › PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet
- endorlabs.com › PHP2Shell: Critical vulnerabilities in PHP (CVE-2026-109618, CVE-2026-109619)