Summary
The PHP security team has announced an emergency security release for two critical vulnerabilities in PHP, scheduled for Wednesday 21 October 2026 at 14:00 GMT. The release is expected to address CVE-2026-109618 and CVE-2026-109619, both rated CVSS 9.2 by the PHP project.
Details of the vulnerabilities circulated publicly before the fix, and they are already widely discussed. Researchers report that both flaws allow remote code execution in PHP core. Mass exploitation is expected to begin very shortly after the details are published.
This is a pre-release notice to help member institutions prepare. GARNET CSIRT will update this advisory once the PHP release is out and the affected and fixed versions are confirmed.
Impact
Exploitability signals: CVSS 9.2 for both vulnerabilities (PHP project) · remote code execution in PHP core · details already circulating publicly · rapid mass exploitation expected after release.
Successful exploitation is reported to give an attacker code execution on the web server, under the account that runs PHP. PHP underpins a large share of the services run by member institutions, including learning management systems, journal platforms, institutional websites, webmail, federation identity providers, and network monitoring tools. A compromised PHP host typically exposes application databases, stored credentials, and a foothold into the wider campus network.
Affected systems
Affected and fixed versions have not yet been published by the PHP project. Based on current public reporting, which has not yet been confirmed by the vendor:
- PHP 5.4 and later are reported to be affected, across all SAPIs
- PHP 8.2, 8.3 and 8.4 and later are expected to receive fixes in today’s release
- PHP 8.1 and older, including all 7.x and 5.x versions, are end of life and are reported to receive no official fix
What is not yet known
- The exact component affected and the conditions required for exploitation. Public discussion has focused on PHP services that accept file uploads, but this is not confirmed.
- Whether any temporary configuration change is an effective mitigation. Some have been suggested, but their effectiveness is unclear. Do not rely on them in place of patching.
- How quickly operating system distributions (Ubuntu, Debian, RHEL and others) will ship patched packages.
Action
-
Identify every PHP-based service you run. Common examples in our community include Moodle, Open Journal Systems (OJS), WordPress, Joomla, Drupal, SimpleSAMLphp, Roundcube, Nextcloud, phpMyAdmin, LimeSurvey, GLPI, osTicket, and monitoring frontends such as Zabbix, LibreNMS, Cacti and phpIPAM.
-
Record the PHP version on each host. Any host running PHP 8.1 or older should be scheduled for upgrade to a supported branch, or for a vendor or distribution backport if one becomes available.
-
Limit access to PHP services as much as possible until patches are installed. Restrict administrative and internal-only applications to the campus network or VPN.
-
Prepare to patch immediately after 14:00 GMT. Test and install the PHP security updates as soon as they are available. Check your package sources, since distribution packages may arrive later than the official release.
-
Plan for central services now. For systems that cannot be taken offline easily, such as the LMS, identity provider, or webmail, agree internally on maintenance windows and who can approve emergency changes before the details are published.
-
Remove PHP from hosts that do not need it.
-
Watch for advisories from PHP application projects. Many will publish their own guidance once the PHP details are public.
-
Report suspicious activity. Signs such as web server or PHP-FPM processes spawning shells, or unexpected files appearing in web or temporary directories, should be reported to GARNET CSIRT.
This advisory is published with a detached PGP signature against the CSIRT key. Confirm it is genuine and unmodified before acting:
Downloads: source .md · signature .md.asc · public key. Check the fingerprint (684C7B7DA77E4F1B68AED3ECE84B541C6184CC6F) on the PGP page — if gpg reports a “Good signature” from that key, this advisory is authentic.
Think a system in the community is affected or compromised?Report an incident