DE EN IT

~/exploited / cve-2026-109618

CVE-2026-109618: PHP Group PHP

According to CISA this vulnerability is already used in attacks (added on 26 October 2026).

Key facts

CVECVE-2026-109618
VendorPHP Group — PHP
VulnerabilityPHP Memory Corruption Vulnerability
Added26 October 2026
Deadline (US agencies)29 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score9.2 (critical) · CVSS 4.0
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack over the network, complexity: high, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 100%. Higher than 100% of all scored vulnerabilities (as of 19 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-416 — Use After Free
CWE-755
CWE-824
Affected versionsphp: >= 7.3.0, < 8.2.35
php: >= 8.3.0, < 8.3.36
php: >= 8.4.0, < 8.4.27
php: >= 8.5.0, < 8.5.12
pan-os: >= 10.2.0, < 10.2.7
pan-os 10.2.7
pan-os 10.2.8
pan-os 10.2.9
and 49 more

Description (NVD)

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).

Patches and vendor advisories

Description (CISA)

PHP contains an out-of-memory corruption vulnerability that allows for unauthenticated remote code execution.

Required action (CISA)

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether PHP Group PHP is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 26 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).