Skip to content
StrikeCyberStrikeCyber
Threat Radar · Actively exploited

PHP Group PHP (CVE-2026-109618)

Exploited in the wild Added October 26, 2026 EPSS 100.0%Web apps

Quick answer

Yes. CVE-2026-109618 in PHP Group PHP is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on October 26, 2026. If you run PHP, apply the vendor's fix now and check for signs of compromise.

ConfirmedExploited in the wild
Not knownRansomware use
100.0%EPSS · top 1%
October 26,Added to CISA KEV

Our analysis

Updated November 14, 2026

Who is likely exposed

Any organization running PHP to power web applications or APIs is potentially in scope. Because this is an unauthenticated remote code execution flaw, internet-facing PHP hosts, web servers, and application stacks are the highest-priority concern. Shared hosting, legacy sites, and forgotten subdomains running PHP are common blind spots.

How to check quickly

  • Inventory where PHP runs across your estate, including container images and CI pipelines.
  • Confirm the PHP version on each host and compare it against the vendor advisory for fixed versions.
  • Flag anything reachable from the internet first, then move to internal services.

What to prioritize

Patch internet-exposed PHP first. The EPSS probability for this vulnerability is extremely high, so treat it as an active, imminent threat. Follow your BOD 26-04 patching timelines, and where no fix is available, apply vendor mitigations or take the affected service offline.

Detection hints

This is a web-application memory corruption issue (CWE-416 use-after-free, CWE-824 uninitialized pointer, CWE-755), so exploitation may produce crashes, worker restarts, or abnormal memory behavior.

  • Watch for repeated PHP-FPM or web worker segfaults and unexpected process restarts.
  • Alert on new or unusual child processes spawned by web server accounts.
  • Review outbound connections from PHP hosts for signs of post-exploitation activity.

See the Threat Radar for related entries.

Written by StrikeCyber's offensive security team from public advisories and our own testing experience.

What is CVE-2026-109618?

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

Description from the CISA Known Exploited Vulnerabilities catalogue.

What kind of flaw is it?

Use after freeCWE-416

A memory-safety bug where the program uses memory it has already released, which attackers turn into code execution.

Other exploited use after free

Why it matters

Web platforms and content management systems are exposed by design. Exploited vulnerabilities are used to plant web shells, steal data and pivot into back-end systems, often within hours of public disclosure.

Likelihood of exploitation activity in the next 30 days (EPSS)100.0%

Higher than 100% of all scored vulnerabilities.

Am I affected? How to check

  1. 1Inventory websites and portals running the affected platform, plugin or library, including ones hosted by agencies or vendors.
  2. 2Check versions against the advisory, including plugins and dependencies.
  3. 3Review web server logs and file changes for signs of exploitation.

What to do now

  1. 1Update the platform, plugin or library to the fixed version.
  2. 2Remove unused plugins and test sites.
  3. 3Put critical applications behind a web application firewall while patching is underway.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

Deadline and priority

CISA requires US federal civilian agencies to remediate catalogued vulnerabilities by the listed due date under Binding Operational Directive 22-01 (October 29, 2026 for this one), and strongly urges every organization to prioritize them the same way.

In the news

More in the daily briefing.

Common questions

What is CVE-2026-109618?

CVE-2026-109618 is a memory corruption vulnerability in PHP (PHP Group) that allows unauthenticated remote code execution. It stems from an out-of-memory condition and is tracked under multiple weaknesses including use-after-free (CWE-416) and improper handling of exceptional conditions (CWE-755). CISA added it to the Known Exploited Vulnerabilities catalog on 2026-10-26.

Is CVE-2026-109618 being exploited?

Yes. CISA lists it as actively exploited, and its EPSS score indicates a very high probability of exploitation in the near term. Known ransomware use is not currently documented, but the unauthenticated remote code execution risk still warrants urgent action.

How do I fix CVE-2026-109618 in PHP?

Apply the fixes provided by the PHP Group and check the vendor advisory for fixed versions that apply to your deployment. CISA directs stakeholders to follow BOD 26-04 patching guidance, and to discontinue use of the product if mitigations are unavailable.

Is CVE-2026-109618 being exploited?

Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on October 26, 2026.

How do I fix CVE-2026-109618?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Check the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.

Is my PHP Group PHP affected?

Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.

Sources

(877) 657-8496