Threadlinqs IntelligenceStart free

Vendor1 product tracked

PHP Group vulnerabilities & exploitation

3 in CISA KEV1 ransomware-linked3 with public exploit

As of 2026-11-19, Threadlinqs tracks 17 PHP Group CVEs, 3 in the CISA Known Exploited Vulnerabilities catalog, 1 used in ransomware campaigns, linked to 30 tracked threat campaigns and 9 named threat actors.

CVEs
17Since 2024
CISA KEV
318% of CVEs
Critical
2CVSS v3 9.0+
Avg CVSS
6.6/10Max 9.8
Threats
30Linked campaigns
Actors
9Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 17 PHP Group CVEs published between and . The busiest month was 2026-09 (11 new CVEs). 3 of them (18%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 17 of 17 tracked PHP Group CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 17 CVEs; 1 distinct PHP Group product is affected. The most frequently affected:

  • PHP 17 CVEs

Threat activity

30 tracked threat campaigns reference PHP Group products or exploit PHP Group CVEs; the 25 most recent are listed.

Threat actors targeting PHP Group

Named threat actors attributed to campaigns that involve PHP Group products or CVEs, with the number of linked campaigns:

How to prioritise PHP Group patching

This order follows the data Threadlinqs holds for PHP Group, not a generic severity checklist:

  • 3 of 17 PHP Group CVEs (18%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2026-109618, CVE-2026-109619, CVE-2024-4577.
  • 1 CVE is known to be used in ransomware campaigns; patch these ahead of other KEV entries on internet-facing systems.
  • Outside KEV, the highest EPSS scores are CVE-2026-17544 (0.4%), CVE-2026-17543 (0.4%), CVE-2026-7260 (0.2%).
  • 2 CVEs score Critical and 4 High on CVSS v3 (maximum 9.8, average 6.6); sequence these after KEV and high-EPSS items.
  • 3 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-19 and refresh daily.