Back to live map

CVE-2026-109618

KEVPHP Memory Corruption Vulnerability

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

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

CVSS 4.0 vectorCVSS: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
PublishedOct 21, 2026
Last modifiedOct 26, 2026
Added to KEVOct 26, 2026
Remediation dueOct 29, 2026
  • CISA Confirms Active Exploitation of Two PHP2Shell Flaws Enabling Remote Code Execution

    The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Monday confirmed active exploitation of the recently patched PHP2Shell flaws by adding them to its Known Exploited Vulnerabilities (KEV) catalog. The PHP vulnerabilities, both rated 9.2 on the CVSS scoring system, facilitate unauthenticated remote code execution on affected deployments - CVE-2026-109618 - An out-of-memory

    The Hacker News · 2h ago
  • CISA Adds Two Known Exploited Vulnerabilities to Catalog

    CISA has added two new vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog and updated the PHP Alert, Critical Vulnerabilities in PHP Require Immediate Patching :   CVE-2026-109618 - PHP Memory Corruption Vulnerability  CVE-2026-109619 - PHP Stale Internal Request-State Vulnerability  These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose signif

    CISA Alerts · 18h ago
  • PHP2Shell security flaws now sucessfully exploited in the wild

    Two critical RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619), collectively tracked as PHP2Shell, have been successfully exploited in the wild. [...]

    BleepingComputer · 21h ago
  • Threat Brief: Critical Vulnerabilities in PHP: CVE-2026-109618, CVE-2026-109619 (Updated October 25)

    CVE-2026-109618 and CVE-2026-109619 are Critical vulnerabilities in PHP, a scripting language used globally for web servers and CMS systems. The post Threat Brief: Critical Vulnerabilities in PHP: CVE-2026-109618, CVE-2026-109619 (Updated October 25) appeared first on Unit 42 .

    Unit 42 · 3d ago
  • Critical PHP Vulnerability (CVE-2026-109618, CVE-2026-109619) [infocon yellow], (Wed, Oct 21st)

    PHP.net announced that it will release a critical update today. We decided to change the infoCon to YELLOW due to the widespread use of PHP, the expected severity of the flaw (CVSS 9.4), and the availability of early PoC exploits before the patch became available.

    SANS ISC · 5d ago
  • Critical Vulnerabilities in PHP Require Immediate Patching

    Update October 26, 2026:   CISA has updated this Alert to reflect the addition of CVE-2026-109618 and CVE-2026-109619 to its Known Exploited Vulnerabilities (KEV) Catalog on Oct. 26, 2026.    Update October 23, 2026 :  CISA has updated this Alert to: (1) provide a SIGMA detection rule to help identify potentially suspicious activity; (2) incorporate partner resources; and (3) reinforce existing mi

    CISA Alerts · 5d ago
86
Risk assessment · Critical

Actively exploited. Patch immediately.

Exploitation
Confirmed in the wild (CISA KEV)
Federal remediation deadline
2 days left (2026-10-29)
CVSS
9.2 CRITICAL
EPSS (30-day exploit probability)
100.0% · top 1% of all CVEs
Weakness
CWE-416
Attack vector
Network, remotely reachable
Preconditions
No privileges and no user interaction
  1. 1.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.
  2. 2.Treat as emergency change: patch or isolate internet-facing instances first.
  3. 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
  4. 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.