← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-109619 exploited? Yes: in CISA KEV since 26 Oct 2026

Gociux · PHP Group PHP · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-109619, PHP Stale Internal Request-State Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 26 Oct 2026, 5 days after it was published. It affects PHP Group PHP. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 26 Oct 2026
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity9.2CVSS 4.0 · critical
US federal due29 Oct 2026BOD 22-01 deadline

What it is

PHP contains a stale internal request-state vulnerability that allows for unauthenticated remote code execution.

VendorPHP Group (3 exploited CVEs in KEV)
ProductPHP
VulnerabilityPHP Stale Internal Request-State Vulnerability
WeaknessCWE-416, CWE-755, CWE-824, CWE-1325, CWE-1419
Published21 Oct 2026
Added to KEV26 Oct 2026
Reported by (CNA)php

What to do

  1. Check whether you run it. Look for PHP in your asset inventory, including appliances and cloud images. Stack check lists every exploited PHP Group CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 21 Oct 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for PHP Group.

Other exploited CVEs in PHP

References

Questions

Is CVE-2026-109619 being exploited?

Yes. CISA added CVE-2026-109619 to the Known Exploited Vulnerabilities catalog on 26 Oct 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-109619 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-109619?

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. Check PHP Group's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected PHP and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in October 2026 · PHP Group scorecard · act-now radar.

Running PHP Group in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →