# CVE-2026-109618: PHP Memory Corruption - **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Yes, since 26 Oct 2026 (CISA KEV) - **Fix available:** Yes - **Published:** 21 Oct 2026 - **Updated:** 29 Oct 2026 - **Also known as:** AZL-109815, BELL-CVE-2026-109618, BIT-libphp-2026-109618, BIT-php-2026-109618, BIT-php-min-2026-109618, CLEANSTART-2026-LE11033, DEBIAN-CVE-2026-109618, ECHO-3b6e-9e7f-34fe, ROOT-OS-ALPINE-315-CVE-2026-109618, ROOT-OS-ALPINE-318-CVE-2026-109618, ROOT-OS-UBUNTU-2004-CVE-2026-109618, ROOT-OS-UBUNTU-2504-CVE-2026-109618, ROOT-OS-UBUNTU-2510-CVE-2026-109618, UBUNTU-CVE-2026-109618, openSUSE-SU-2026:12228-1 ## What is CVE-2026-109618? CVE-2026-109618 is a critical vulnerability in Paloaltonetworks Pan-Os, published on 21 Oct 2026. ### Official description PHP 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). Weakness: CWE-824 (Access of Uninitialized Pointer), CWE-755 (Improper Handling of Exceptional Conditions), CWE-416 (Use After Free), CWE-1419 (Incorrect Initialization of Resource), CWE-1325 (Improperly Controlled Sequential Memory Allocation) ## Which versions are affected by CVE-2026-109618? 3 open source packages ship an affected version, including libphp, php and php-min. It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libphp` | Bitnami | From 7.3.0 | 8.2.35, 8.3.36, 8.4.27, 8.5.12 | | `php` | Bitnami | From 7.3.0 | 8.2.35, 8.3.36, 8.4.27, 8.5.12 | | `php-min` | Bitnami | From 7.3.0 | 8.2.35, 8.3.36, 8.4.27, 8.5.12 | | `matomo` | openSUSE:Tumbleweed | All versions | 5.14.2-1.1 | Products: Paloaltonetworks Pan-Os, Paloaltonetworks Panorama Virtual Appliance, Php Php, Siemens Ruggedcom Ape1808 Firmware. ## How do I fix CVE-2026-109618? Upgrade libphp to a fixed version for your release line: 8.2.35, 8.3.36, 8.4.27 or 8.5.12. US federal agencies must fix it by 29 Oct 2026. ## Is CVE-2026-109618 being exploited? Yes. Attackers have exploited CVE-2026-109618 in the wild since at least 26 Oct 2026. Public exploit code: - CVE-2026-109618/109619 — 5 RCE chains + detection rules (Suricata, Sigma, ModSecurity). PHP session.upload_progress pre-auth exploit research. (github_poc): https://github.com/ikow/php2shell-poc - Proof-of-Concept (PoC) exploit for php2shell (CVE-2026-109618 / CVE-2026-109619), demonstrating remote code execution in vulnerable PHP environments. For security research and educational purposes only. (github_poc): https://github.com/eness/php2shell-CVE-2026-109618-CVE-2026-109619-PoC - High fidelity scanner for php2shell (CVE-2026-109618 and CVE-2026-109619) (github_poc): https://github.com/assetnote/php2shell-scanner - PHP2Shell exploit framework — CVE-2026-109618/619 PHP session.upload_progress UAF to RCE (github_poc): https://github.com/JoasASantos/php2shell-exploit - PHP2Shell: version-aware research toolkit for CVE-2026-109618 / CVE-2026-109619 — pre-auth RCE in PHP session.upload_progress (mod_php). Build profiles, labs, heap calibration and detection guidance for authorized security testing. (github_poc): https://github.com/devploit/php2shell - Protects an unpatched PHP against php2shell (CVE-2026-109618 / CVE-2026-109619): a small extension that mirrors the official fix component by component and steps aside once the engine carries it. PHP 5.6-8.5; Sury, cPanel EA4, DirectAdmin, Docker, Windows. (github_poc): https://github.com/HOSTED-POWER/php_uploadprogress_guard ## Other vulnerabilities in Paloaltonetworks Pan-Os - [CVE-2024-3400](https://insights.sbomify.com/CVE-2024-3400/): Palo Alto Networks PAN-OS Command Injection (critical 10.0, exploited in the wild) - [CVE-2020-2021](https://insights.sbomify.com/CVE-2020-2021/): Palo Alto Networks PAN-OS Authentication Bypass (critical 10.0, exploited in the wild) - [CVE-2017-15944](https://insights.sbomify.com/CVE-2017-15944/): Palo Alto Networks PAN-OS Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2026-0300](https://insights.sbomify.com/CVE-2026-0300/): Palo Alto Networks PAN-OS Out-of-bounds Write (critical 9.3, exploited in the wild) - [CVE-2024-0012](https://insights.sbomify.com/CVE-2024-0012/): Palo Alto Networks PAN-OS Management Interface Authentication Bypass (critical 9.3, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-109618 and fix it if it is affected. What it is: CVE-2026-109618 is a critical vulnerability in Paloaltonetworks Pan-Os, published on 21 Oct 2026. Exploitation: Yes. Attackers have exploited CVE-2026-109618 in the wild since at least 26 Oct 2026. Affected packages and fixed versions: - libphp (Bitnami): affected from 7.3.0; fixed in 8.2.35, 8.3.36, 8.4.27, 8.5.12 - php (Bitnami): affected from 7.3.0; fixed in 8.2.35, 8.3.36, 8.4.27, 8.5.12 - php-min (Bitnami): affected from 7.3.0; fixed in 8.2.35, 8.3.36, 8.4.27, 8.5.12 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-109618/ (Markdown: https://insights.sbomify.com/CVE-2026-109618/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109618 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109618 - OSV: https://osv.dev/vulnerability/CVE-2026-109618 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-109618/ Summaries are generated and may contain mistakes; the official description above is the record.