Exploited CVEs / CVE-2026-109619

CVE-2026-109619

PHP Stale Internal Request-State Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-10-29 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Senserva top pickour recommendation since 2026-10-21

Internet-facing PHP is everywhere, exploit code was public before the fix, and the vendor shipped an emergency release: update every PHP host now, exposed ones first.

Senserva AI read on CVE-2026-109619CISA required actionOfficial fix for CVE-2026-109619What the press saysAdmin questions#2 hottest CVE right now

Risk summary

In the top 10 of the Senserva CVE Ranking (as of 2026-11-14)
HighCISA KEV
8.1
CVSS v3 base
9.2
CVSS v4
100%
EPSS exploit probability
High
Severity
2026-10-26
Added to KEV
2026-10-29 (past due)
CISA due date

Actively exploited PHP Group PHP vulnerability, High severity, CVSS v3 8.1 (CVSS v4: 9.2). Added to the CISA KEV catalog 2026-10-26.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-10-29; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated November 16, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion for CVE-2026-109619

CVE-2026-109619 is the PHP use-after-free on stale request state, and it is paired with CVE-2026-109618, an out-of-memory memory corruption bug. Both are known as php2shell. CISA added both to KEV on 2026-10-26, and its alert says they allow unauthenticated remote code execution. The affected servers are every PHP install that serves web requests: Apache mod_php, PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. CISA's alert notes that PHP rates mod_php as the highest risk. The Severity here is High at CVSS 8.1 from NVD. Rapid7 lists the vendor-side CVSSv4 score as 9.2 (Critical), so do not use the NVD number to push this down your queue. The mechanism is that global state pointing into request memory is not reset, or is repopulated, after the memory is freed, so a later request can read freed memory. Rapid7 says the PHP advisory confirms RCE against mod_php through the PHP 8.5 fatal error backtrace feature. That feature is on by default through fatal_error_backtraces. The advisory also confirms RCE through the session lifecycle on both mod_php and FPM. Rapid7 reports multiple public proofs of concept, and Beazley Security reports broad exploitation attempts starting in the days after the 2026-10-21 release. No ransomware use is recorded. The CISA remediation due date for federal civilian agencies was 2026-10-29, which has passed, so treat anything unpatched as potentially already probed.

Do this: Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, then restart PHP-FPM and Apache so the running workers load the fixed build. Check mod_php hosts first. If you run PHP 7.4, 8.0 or 8.1, which are end of life, the PHP project has supplied limited source backports for this incident, so build from those or plan a migration. Until patched, review the mitigations in PHP's advisory, such as the setting for CVE-2026-109619. Beazley notes that these cover only the confirmed session paths and do not replace patching. On internet-facing PHP hosts, check web and PHP error logs since 2026-10-21 for crashes, fatal error backtraces and unexpected new files in web roots. Follow the forensic triage guidance in the CISA alert and the NCSC-NL php2shell repository if you find signs of compromise.

Key sources

AI-generated from public data, 2026-11-13. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-109619

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for CVE-2026-109619

Published
2026-10-21
Last revised
2026-11-16
Changes tracked
7

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is CISA adding CVE-2026-109619 to its KEV catalog on 2026-10-26, confirming real-world exploitation. EPSS then jumped from 0.0% to 100.0% on 2026-10-27, reinforcing that urgency. The CVSS Severity score kept flipping between 9.8 and 8.1, ending at 8.1, so treat that churn as noise and prioritize patching today.

0%25%50%75%100%CISA KEVCISA KEV on 2026-10-262026-10-21: EPSS 0.0%2026-10-27: EPSS 100%2026-10-27: EPSS 100%EPSS 100%2026-10-212026-10-27

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-10-21 EPSS first scored at 0.0%
  • 2026-10-23 CVSS 9.8 to 8.1
  • 2026-10-26 added to the CISA KEV catalog by CISA
  • 2026-10-27 CVSS 8.1 to 9.8; EPSS 0.0% to 100.0%; CVSS 9.8 to 8.1

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

From the Senserva blog

CISA required action

Federal remediation due date: 2026-10-29 (past due).

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.

Official fix for CVE-2026-109619

Update Php to version 8.2.35 or later. Update Php to version 8.3.36 or later. Update Php to version 8.4.27 or later. (Fixed-version data from NVD.)

Common questions about CVE-2026-109619

Is CVE-2026-109619 actively exploited?

Yes. CVE-2026-109619 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-26, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%.

What is the CISA deadline and required action for CVE-2026-109619?

CISA set the federal remediation due date at 2026-10-29, which has passed; treat any unremediated system as overdue. The verbatim required action: 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 fixes CVE-2026-109619?

Check the vendor's security advisory for the patched PHP versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-109619?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-109619's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).

Scope and sources

More exploited PHP Group CVEs
Authoritative references

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.