PHP2Shell: code execution in the PHP core
CVE-2026-109618 and CVE-2026-109619 are two vulnerabilities in PHP itself: code execution on the server without authentication, CVSS 9.2. The fixes came on 21 October 2026: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Update PHP, restart processes, check the version. Official sources only, and the positions of KZ-CERT, CISA and other government bodies.
Sources: php.net, PHP Foundation · notices GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp · NVD CVE-2026-109618 and CVE-2026-109619 · government bodies: KZ-CERT of the State Technical Service JSC, CISA, CERT-EU, IPA, JPCERT/CC, KISA · researchers: Wiz · Debian · Ubuntu · CISA KEV
Checklist
- All PHP installations found, starting with those reachable from the internet
- PHP updated to 8.5.12, 8.4.27, 8.3.36, 8.2.35 or to a distribution package with the fix
- php-fpm or the web server restarted, phpinfo() shows the new version
- Where updating is not possible: temporary measures applied and external access restricted
- Logs checked for signs of compromise
- For PHP 8.1 and older: there is a plan to move to a supported branch
Who is affected
Any server where PHP handles web requests. The framework and CMS do not matter: the vulnerability is in PHP itself, so updating WordPress, Bitrix or Laravel does not close it. PHP must be updated.
| PHP branch | Vulnerable | Fixed in |
|---|---|---|
| 8.5 | before 8.5.12 | 8.5.12 |
| 8.4 | before 8.4.27 | 8.4.27 |
| 8.3 | before 8.3.36 | 8.3.36 |
| 8.2 | before 8.2.35 | 8.2.35 |
| 7.4, 8.0, 8.1 | all versions | no official release; a distribution package or a fix in the source |
| 7.3 and older | all versions from 5.4 (CVE-2026-109619) and from 7.3 (CVE-2026-109618) per NVD | none; move to a supported branch |
- PHP is found not only on websites: shared hosting (the provider updates it), control panels, Docker images, equipment and boxed products. NVD lists as affected, for example, Palo Alto Networks PAN-OS (branch 10.2) and Siemens RUGGEDCOM APE1808; the vendors have their own notices.
- PHP 8.2 stops receiving security fixes on 31 December 2026 (php.net).
php.net, 21.10.2026Who is at risk: all PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs.editors' translation
KZ-CERT of the State Technical Service JSC, 22.10.2026Since the vulnerabilities are located directly in the PHP core, changing the web application's source code does not fully eliminate them. To protect, the PHP server environment must be updated.editors' translation
What to do
The order follows the PHP notice and the recommendations of KZ-CERT and KISA.
| Distribution | Package | Safe version |
|---|---|---|
| Debian 13 | php8.4 | 8.4.27-1~deb13u1 (DSA-6574-1) |
| Debian 12 | php8.2 | 8.2.35-1~deb12u1 (DLA-4848-1) |
| Ubuntu 24.04 | php8.3 | 8.3.6-0ubuntu0.24.04.13 |
| Ubuntu 22.04 | php8.1 | 8.1.2-1ubuntu2.28 |
| Ubuntu 20.04 and older | php7.4 and lower | only in Ubuntu Pro (ESM) |
- Find all PHP installations, starting with those reachable from the internet.
- Update PHP to the fixed version or to a distribution package with the fix.
- Restart php-fpm, apache2 or httpd. Rebuild containers on a new base image and redeploy.
- Check which version the service actually answers with: the phpinfo() page, the PHP Version and Server API lines (“Apache 2.0 Handler” means mod_php, “FPM/FastCGI” means php-fpm). The version from php -v may differ. Delete the phpinfo() page right after the check.
KZ-CERT of the State Technical Service JSC, 22.10.2026Check that the updates were actually applied and restart the relevant PHP-FPM or web server worker processes to rule out use of outdated code.editors' translation
KISA, 22.10.2026 (translation)Distribution and vendor packages may keep the same version number after a fix. Check the package changelog to see whether the CVE is included.editors' translation
If you cannot update right away
PHP and KZ-CERT list temporary measures and both stress that they do not replace the update.
- session.upload_progress.enabled = 0 in php.ini, the FPM pool or the server configuration, then restart all worker processes. PHP: do not rely on ini_set() and .user.ini.
- PHP 8.5: fatal_error_backtraces = 0 and a restart of worker processes.
- memory_limit = -1 so that the application cannot override it (php_admin_value). Limit memory with the container or cgroup; do not use RLIMIT_AS and RLIMIT_DATA, because according to PHP they themselves cause the vulnerable crash.
- post_max_size = 8M if file upload is not needed, or 32M if it is; upload_max_filesize smaller than post_max_size. Limits on request size and number of elements also on the web server or proxy.
- KZ-CERT: consider temporarily blocking multipart/form-data requests at the Nginx or Apache level, bearing in mind that file upload may break.
- KZ-CERT, IPA, KISA: if neither the update nor temporary measures are possible, restrict external access or temporarily stop the service.
php.net, 21.10.2026While only an update is a complete solution, the following measures reduce exposure to specific attack paths but do not make an installation safe.editors' translation
KZ-CERT of the State Technical Service JSC, 22.10.2026Important: the temporary measures listed do not provide full protection and do not replace installing the fixes. In particular, removing the memory_limit cap may increase the risk of exhausting system memory and denial of service.editors' translation
Checking for compromise
Signs that JPCERT/CC gives, citing the discoverers (translation). JPCERT/CC warns: there are several attack paths, one detection rule does not catch all of them, and there may be no traces, so their absence does not prove there was no attack.
- In past HTTP responses: a PHPSESSID cookie with an unnaturally long or anomalous value.
- Suspicious multipart/form-data requests, with PHP memory limit errors or HTTP 500 responses before or after them.
- Unexpected crashes or frequent restarts of PHP worker processes.
- Also: suspicious processes starting, external connections, creation of suspicious files (JPCERT/CC); unusual web server child processes and signs of unauthorized command execution (KZ-CERT).
- If compromise is suspected: keep the logs as evidence, assess the scale, isolate the system (JPCERT/CC).
- Report the incident to KZ-CERT through the “Report an incident” section on cert.gov.kz.
Positions of government bodies
What national response teams and cybersecurity agencies recommend.
- CISA takes the strictest position: take systems on PHP 8.1 and older, and those that cannot be updated right away, out of service until they are updated. CISA also notes that PHP is often part of other software and its presence may not be directly visible; a WAF can give partial protection until the update.
- CISA published a SIGMA detection rule for finding suspicious activity in logs.
- As of 25 October, CVE-2026-109618 and CVE-2026-109619 are not in the CISA Known Exploited Vulnerabilities (KEV) catalog.
- Notices from other government bodies that CISA refers to are at the links below.
Kazakhstan · KZ-CERT of the State Technical Service JSC, 22.10.2026Immediately update PHP to the fixed versions 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or install the corresponding updates from the software vendor. Take an inventory of the server infrastructure, determine the PHP versions in use and identify potentially vulnerable web applications, especially those reachable from the Internet.editors' translation
Kazakhstan · NIT JSC (eGov), reply to Digital Business 22.10.2026National Information Technologies JSC reports that the vulnerabilities named in the request do not affect the operation of the eGov.kz portal. At present the portal and its components are operating normally.editors' translation
USA · CISA, 21.10.2026 (updated 23.10)CISA strongly urges organizations to immediately patch the recently disclosed critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619.editors' translation
USA · CISA, 21.10.2026 (updated 23.10)Organizations that cannot update immediately, or that continue to use PHP 8.1 or earlier unsupported versions, should take PHP-based systems offline until they can be patched or updated.editors' translation
EU · CERT-EU, advisory 2026-018CERT-EU advises organisations to patch affected assets immediately. Where that is not feasible, organisations should consider isolating internet-facing applications from public networks until a fix is applied and verified.editors' translation
Japan · IPA, 22.10.2026 (translation)Until the update or migration is complete, do not leave the system running in a vulnerable state: consider temporary measures suitable for your environment and restrict access. If effective temporary measures are hard to adopt, decide, taking into account the damage from an attack and the effect on operations, whether to close external access or temporarily stop the service.editors' translation
Japan · JPCERT/CC, 22.10.2026 (translation)JPCERT/CC confirms that the product is widely used in Japan. If you use the affected products, apply measures promptly based on the developer's information and check whether there has been a compromise.editors' translation
South Korea · KISA, 22.10.2026 (translation)Update the servers reachable from the internet first. After the update, be sure to restart all web services where PHP runs: without a restart the old version keeps running in memory and the server remains vulnerable.editors' translation
- Kazakhstan · NIT JSC reply about the eGov.kz portal (Digital Business)
- USA · CISA: Critical Vulnerabilities in PHP Require Immediate Patching
- USA · NSA: Critical Patches Recommended for PHP Vulnerabilities
- United Kingdom · NCSC: Critical security issue affecting PHP
- Canada · Cyber Centre: AL26-026
- Australia · ASD ACSC: Critical vulnerabilities in PHP
- New Zealand · NCSC
- Netherlands · NCSC-NL: php2shell (GitHub)
What companies in Kazakhstan did
Statements by Kazakhstan companies about their own actions, verbatim, with links. The editors did not verify them. If your company published a report on its actions, write to us and we will add it.
- Documentolog: the update was prepared in advance, according to reports in open sources, and began right after the fixes were released at 18:34 Astana time. Customers of the cloud platform do not need to do anything; those who run the platform on their own servers should check the PHP version.
- ONEHOST: on a VPS without administration the server owner is responsible for the update; on virtual hosting, check the PHP version in the panel and move off 8.1 and older.
- ONELAB: before updating PHP on older 1C-Bitrix sites, make a backup, update the core and modules, and check your own code and the integrations with 1C.
Documentolog (d8n.kz), electronic document management, 23.10.2026By 08:00 on 22 October all 495 systems were running fixed versions; from the publication of the bulletin to the last update, 13 hours 26 minutes passed.editors' translation
ONEHOST (onehost.kz), hosting, 22.10.2026If the server is subscribed to the server administration service, our engineers have already installed the PHP fixes, restarted the services and checked the system for suspicious activity.editors' translation
ONEHOST (onehost.kz), hosting, 22.10.2026We perform server software updates on virtual hosting.editors' translation
ONELAB (onelab.kz), web studio, 22.10.2026If your website or corporate portal is under our technical support, PHP has already been updated to a protected version, code compatibility has been checked, and the system is protected from PHP2Shell.editors' translation
ONELAB on 1C-Bitrix sites, 22.10.2026Cloud Bitrix24 is operated by the vendor itself, so the question concerns mainly boxed solutions on your own server or hosting.editors' translation
ONELAB on compatibility, 22.10.2026After moving to PHP 8.2+ such a site may stop working: the catalog, the cart or the exchange with 1C may break.editors' translation
- Documentolog: “Documentolog closed the PHP2Shell vulnerabilities on all 495 systems in 13 hours”
- ONEHOST: “PHP2Shell: critical PHP vulnerabilities. What VPS and server owners should do”
- ONELAB: “PHP2Shell: the PHP vulnerability and 1C-Bitrix sites”
- PS Cloud Services: KZ-CERT recommendations in Kazakh and Russian
Position of PHP and the researchers
The PHP Foundation and Wiz, one of the teams that found the vulnerability, see the role of AI differently. Quotes are verbatim.
- PHP Foundation: the first signs of the problem were found by a PHP core developer in 2024; the fix stalled for months because the team worked by consensus and could not choose between options. Now decisions are made by majority.
- PHP Foundation: AI helps check reports and group them by root cause, but every decision and every patch is made by a human. Since 1 July the team has published 15 CVEs and reviewed more than 100 invalid reports.
- The PHP Foundation asks companies, hosting providers and states whose services run on PHP to fund security work: there are too few core specialists.
- Wiz: the research used the Gemini and GPT AI models and Wiz's own tool, Wiz Atlas.
PHP Foundation, 21.10.2026We won't pretend otherwise: the delay was a structural failure, caused by both the security team's decision process and its lack of resources.editors' translation
PHP Foundation, 21.10.2026Tools now find bugs faster than ever, for defenders and attackers alike, and the number of reports will keep growing. What tools cannot do is decide on the right fix for a long-standing design decision in the engine, weigh the compatibility trade-offs, and review the patch.editors' translation
Wiz ResearchThe vulnerable code had been there for more than a decade – what AI changed was the ability to understand the weaknesses and turn them into a working exploit.editors' translation
Wiz ResearchWith frontier AI models and the right tools, a single researcher completed in a week what previously would have taken a world-class team months of work.editors' translation
How to reduce risk next time
Editorial recommendations. This is a vulnerability in the runtime, not in your code: a code scanner will not find it, an asset inventory will. The basis is the recommendations of KISA, IPA and PHP.
- Asset inventory: a list of “service → server or image → PHP version → owner”. KISA advises checking against the servers actually running, not only the asset list, including contractors' sites, test and abandoned servers, admin panels, equipment with embedded PHP and Docker images.
- Regular scanning: of the external perimeter, to find forgotten hosts; of servers and images, to see package and runtime versions (SBOM).
- Subscriptions: php.net, KZ-CERT, notices from your own distribution. This time PHP warned about the release a day ahead.
- Emergency update procedure: who decides, in what time frame, how to test and roll back; updating with one command or by rebuilding images; restart and version check are mandatory steps.
- Supported versions only: move before support ends, not after. PHP 8.1 and older did not get an official fix; support for 8.2 ends on 31.12.2026.
- Less exposed to the outside: test servers, admin panels and unused sites should not be on the internet, or should be behind a VPN.
- Limit the damage: a web process with minimal privileges, secrets not in files next to the code, web servers separated from the internal network and databases.
- Detection and drills: logs in one place, alerts on unusual web server processes and new files in the site directory; twice a year, measure how many hours pass from the news to the last fixed server.
Vulnerability analysis
Both vulnerabilities are use-after-free (CWE-416) in parts of PHP that almost every request goes through: memory management and error handling. PHP's CVSS v4.0 score is 9.2 for both; NIST's CVSS v3.1 scores are 9.8 and 8.1.
| PHP mode of operation | Status per PHP notices |
|---|---|
| Apache mod_php | Code execution confirmed; highest risk |
| PHP-FPM | CVE-2026-109618: code execution through paths in application code; CVE-2026-109619: the path through sessions is confirmed |
| FrankenPHP, LiteSpeed | Likely vulnerable by code analysis, exploits were not tested |
- CVE-2026-109618 in plain words: if a request hits the memory limit at an unlucky moment, PHP aborts it, leaving internal data partly uninitialized, and at the end of the request works with it as if it were valid. Running out of memory can be triggered by a specially built multipart request.
- According to the PHP Foundation: on Apache with mod_php, a request without login starts the attack before the application code, and code execution is shown with default settings; on PHP-FPM, code execution is confirmed through paths in application code.
- CVE-2026-109619 in plain words: the data of one request stays after memory is freed, and the next request in the same worker process uses it. The confirmed path is upload progress tracking in sessions: it is on by default and works even without session_start() (PHP notice).
- According to the PHP Foundation: use of freed memory and a process crash are confirmed, and the discoverer showed code execution on a real application under Apache with mod_php.
CVE-2026-109618 · CVE recordPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).editors' translation
CVE-2026-109619 · CVE recordPHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).editors' translation
Timeline
Based on the PHP Foundation post of 21 October, PHP notices and government publications. Time is UTC.
| Date | What happened |
|---|---|
| 2024 | The first external audit of PHP in years (Quarkslab). A core developer finds the first signs of an out-of-memory problem; no attack method is found, and the fix stalls for months |
| 11.08.2026 | Calif reports code execution with the same root cause; OpenAI independently reports the same root cause |
| 24.08.2026 | Wiz reports additional attack paths |
| 18.09.2026 | OpenAI reports additional attack paths |
| 20.10, ~15:00 | CVE numbers leak to social networks with a wrong score of 10.0 and no technical details |
| 20.10, 19:30 | PHP publishes a pre-announcement and moves the release from 22.10 to 21.10 |
| 20.10, ~20:00 | Calif mistakenly publishes a video with a working exploit; the video is removed, copies spread |
| 21.10, 07:41 | Chainguard publishes fixed images before the release, breaking the embargo |
| 21.10, 14:00 | Release of PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35; CISA notice |
| 22.10 | Notices from KZ-CERT, IPA, JPCERT/CC and KISA |
| 23.10 | PHP reports a third vulnerability, CVE-2026-115560; the fix is in the regular release |
| 25.10 | CVE-2026-109618 and CVE-2026-109619 are not in the CISA KEV catalog |
- Who found it: according to the PHP Foundation, Calif, OpenAI and Wiz. The positions of PHP and Wiz are in the section “Position of PHP and the researchers”.
Where to check the information
Primary sources are the vendor and government services. Check retellings in the media and social networks against them.
- Vendor: php.net (News section), security advisories in the php/php-src repository on GitHub, the PHP Foundation blog.
- Vulnerability records: NVD (nvd.nist.gov) and cve.org: description, scores, affected versions.
- Exploitation: the CISA KEV catalog.
- Kazakhstan: KZ-CERT of the State Technical Service JSC, cert.gov.kz.
- USA: CISA (cisa.gov), notices and the KEV catalog.
- Other countries: CERT-EU (cert.europa.eu), JPCERT/CC (jpcert.or.jp), IPA (ipa.go.jp), KISA (boho.or.kr).
- Packages: security-tracker.debian.org, ubuntu.com/security, notices from Red Hat and your provider.
Questions and answers
My site runs on WordPress, Bitrix or Laravel. Does this affect me?
Yes, if PHP on the server is not updated: the vulnerability is in the PHP core, and updating the CMS does not close it.
Details: Who is affected →Which PHP versions are safe?
8.5.12, 8.4.27, 8.3.36, 8.2.35 and newer, as well as distribution packages with the fix backported.
Details: What to do →I updated the package. Is that enough?
No. You need to restart php-fpm or the web server and check which version the site actually answers with.
Details: What to do →Are temporary measures enough?
No. Both PHP and KZ-CERT write that temporary measures reduce risk but do not replace the update.
Details: If you cannot update right away →How do I tell whether the server was already attacked?
JPCERT/CC lists signs: anomalous PHPSESSID values, suspicious multipart requests, worker process crashes. The absence of traces does not prove there was no attack.
Details: Checking for compromise →Does this affect 1C-Bitrix sites?
Yes, boxed versions on your own server or hosting: they run on PHP. Cloud Bitrix24, according to ONELAB, is operated by the vendor. Older sites should be checked for compatibility after moving to PHP 8.2+.
Details: What companies in Kazakhstan did →What do KZ-CERT and CISA recommend?
Update PHP, take an inventory, restart processes. CISA: take systems on PHP 8.1 and older, and those that cannot be updated right away, out of service until they are updated.
Details: Positions of government bodies →Is it true that AI found the vulnerability?
The first signs of the problem were found by a PHP developer in 2024. In 2026 it was reported by Calif, OpenAI and Wiz; Wiz writes that AI helped turn a long-standing bug into a working exploit.
Details: Position of PHP and the researchers →Data as of 25 October 2026. Quotes in Russian and English are verbatim; Japanese and Korean ones are translated by the editors. Current versions are in the notices from PHP and your distribution.