Nine Exploited Vulnerabilities in Five Days: What ProcessUnity CVE Monitoring Found Across Third-Party Portfolios

6 minute read

November 2026

by Kaitlyn Frank

Between Monday, October 26 and Friday, October 30, 2026 the Cybersecurity and Infrastructure Security Agency (CISA) added nine vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. These aren’t theoretical flaws. CISA only adds a vulnerability to the KEV catalog once there’s reliable evidence attackers are already using it, and six of this week’s nine came with remediation deadlines of three days.

Security teams spent the week patching their own environments. Third-Party Risk Management (TPRM) teams faced a different question: How fast can we find out which of our vendors run this technology?

ProcessUnity’s data science team answered that question across active customer portfolios using CVE Monitoring technology. The results show how far a single week of KEVs reaches into a typical vendor ecosystem, and what effective third-party vulnerability monitoring looks like when the remediation window runs out in a matter of days.

The Week in Numbers

ProcessUnity matched the nine uncovered vulnerabilities to technology used by third parties across its active customer portfolios. Here’s what that surfaced:

  • 53% of the average organization’s third parties potentially ran technology affected by at least one of the nine KEVs, excluding the two PHP vulnerabilities. Including PHP, the figure rises to 76%.
  • More than 400 third parties per customer, on average, were potentially exposed to at least one of the week’s vulnerabilities.
  • Every organization analyzed had at least one potentially exposed third party. For each vulnerability with affected products listed, 95% or more of customers were on that impact list.
  • Eight of nine vulnerabilities carry High or Critical severity ratings under the Common Vulnerability Scoring System (CVSS) 3.1.

Exposure varied widely by vulnerability. Ranked by the average share of a customer’s third parties running affected technology:

  1. PHP memory corruption (CVE-2026-109618, CVSS 9.8 Critical): 68%
  2. PHP stale internal request-state (CVE-2026-109619, CVSS 8.1 High): 68%
  3. Linux kernel shared-fragment flaw (CVE-2026-46300, CVSS 7.8 High): 49%
  4. Google Brotli decoder flaw (CVE-2026-111497, CVSS 9.8 Critical): 35%
  5. GitLab CE/EE remote code execution (CVE-2026-97229, CVSS 10.0 Critical): 27%
  6. Cisco Secure Firewall ASA and FTD denial of service (CVE-2026-76418, CVSS 8.6 High): 19%
  7. Broadcom VMware ESX insufficient logging (CVE-2026-41709, CVSS 2.7 Low): 10%

Two more, the Ivanti Connect Secure privilege escalation flaw (CVE-2026-111357) and the Adobe Commerce and Magento file upload flaw (CVE-2026-48356), required an extra step. Public vulnerability data lists them under the companies that make those products today, Ivanti and Adobe, while technology records still carried the products’ former makers. More on that below.

Why We Lead With 53%, Not 76%

PHP runs on a large share of corporate websites, so the two PHP vulnerabilities alone touch 68% of the average customer’s third parties. That’s a real finding, but it also inflates the headline, because detecting PHP on a vendor’s website says less about risk than detecting a firewall or a source-code platform in their environment.

Removing PHP still leaves more than half of the average customer’s third parties potentially exposed to at least one of the remaining seven vulnerabilities. That’s the more conservative number, and it’s still a strong signal. When a week of KEVs reaches that far into a vendor portfolio, waiting for the next assessment cycle isn’t a realistic response plan for third-party risk teams.

How ProcessUnity CVE Monitoring Turns a KEV Listing into an Action Plan

Third-party vulnerability monitoring only helps if it answers the question quickly and narrows the answer to something a team can act on. ProcessUnity CVE Monitoring works in four steps:

  1. Detection. A nightly refresh identifies new and updated entries in CISA’s KEV catalog, so newly confirmed threats enter the process within a day of publication.
  2. Matching and alerting. The ProcessUnity Global Risk Exchange matches the products named in each vulnerability against the technologies each of your third parties is known to use, producing a list of potentially affected vendors. Alerts reach your team through your TPRM work flow, based on your configuration.
  3. Prioritization. For a widespread vulnerability, that list can be long. CVE Monitoring narrows it by the effectiveness of each vendor’s controls related to the vulnerability, mapped through its Common Weakness Enumerations (CWEs), along with attributes like the type of data the vendor holds.
  4. Output. Your team receives a CVE Exposure Report for the prioritized vendors, with the questions to ask each one, recommended next steps, and bulk outreach ready to send.

Anchoring to the KEV catalog is a deliberate choice. Tens of thousands of CVEs are published every year, but only a small fraction are ever exploited. Starting from confirmed exploitation keeps the signal focused on threats that are already active, rather than flooding analysts with theoretical ones.

Speed: Seeing Exposure Before NVD Catches Up

Most vulnerability tools depend on the National Vulnerability Database (NVD) to list which products a CVE affects. That dependency creates a lag. NVD can take days or weeks after a KEV listing to add affected products and severity scores, and in April 2026 NIST moved NVD to a risk-based enrichment model because submission volume had outpaced its capacity.

This week showed why that gap matters. The Cisco Secure Firewall vulnerability had no affected product entries in NVD as of its KEV listing, despite a three-day CISA deadline. During that window, ProcessUnity matched it to the Cisco ASA and Firepower Threat Defense technologies we already track, surfacing exposure at an average of 20% of customers’ third parties. When NVD added the affected products over the following weekend, direct matching confirmed 19%.

Acquisitions create a second kind of gap. NVD lists the Ivanti Connect Secure and Adobe Commerce vulnerabilities under their current makers, but technology records still carried the former ones, Pulse Secure and Magento. ProcessUnity corrected those records to the current maker, surfacing exposure at an average of 7% of customers’ third parties for the Ivanti flaw, which was added to the KEV catalog on Friday with its own three-day deadline, and 8% for Adobe Commerce and Magento.

For TPRM teams working against a three-day deadline, that difference decides whether vendor outreach starts on day one, or after the deadline has already passed.

Accuracy: Being Clear About What the Data Shows

Fast answers only help if teams can trust them. CVE Monitoring matches vulnerabilities to the technology actually detected at each of your third parties, not to industry averages, or assumptions about what a vendor of a certain size probably runs. That’s what turns a CISA bulletin into a named list of your vendors.

It’s equally important to be precise about what a match means. Detecting an affected product at a third party shows potential exposure. It doesn’t confirm that the vendor runs a vulnerable version or that they’ve been compromised. That’s exactly why CVE Monitoring ends in a prioritized outreach list with targeted questions, rather than a red flag on every vendor. Your analysts confirm the answers that matter, and your program documents every step, so you can show auditors and leadership exactly how your team responded.

What This Means for Your Program

A week like this one is a useful stress test. If CISA added nine exploited vulnerabilities this week, could your team answer three questions before the first deadline?

  1. Which of our third parties run the affected technology?
  2. Which of those vendors have the weakest related controls, or hold our most sensitive data?
  3. Have we contacted them, and can we prove it?

If those answers depend on spreadsheets and the last annual assessment, continuous third-party vulnerability monitoring closes the gap. To see how ProcessUnity CVE Monitoring maps newly exploited vulnerabilities to your vendor portfolio, request a demo with the ProcessUnity team.

Frequently Asked Questions

Third-party vulnerability monitoring is the practice of tracking newly disclosed and actively exploited vulnerabilities and identifying which of your vendors, suppliers, and service providers run the affected technology. It extends vulnerability management beyond your own environment to the third parties that support your operations.

The KEV catalog is CISA’s list of vulnerabilities with reliable evidence of active exploitation. Because it filters tens of thousands of published CVEs down to the ones attackers are already using, it’s one of the strongest signals for prioritizing third-party vulnerability monitoring and vendor outreach.

A nightly refresh picks up new and updated KEV entries. The ProcessUnity Global Risk Exchange then matches the products named in each vulnerability against the technologies each of your third parties is known to use, and CVE Monitoring prioritizes the results by control effectiveness and vendor attributes.

No. A match means an affected product was detected at the third party, which indicates potential exposure. CVE Monitoring gives your team targeted questions and outreach so you can confirm whether a vulnerable version is deployed and whether the vendor has remediated it.

NVD can take days or weeks after a KEV listing to add affected products and scores, and NIST now prioritizes enrichment for only a subset of CVEs. CVE Monitoring maps vulnerabilities to the technologies ProcessUnity already tracks at your third parties, so exposure is visible before NVD catches up.

Related Articles

About Us

ProcessUnity is the Third-Party Risk Management (TPRM) company. Our software platforms and data services protect customers from cybersecurity threats, breaches, and outages that originate from their ever-growing ecosystem of business partners. By combining the world’s largest third-party risk data exchange, the leading TPRM workflow platform, and powerful artificial intelligence, ProcessUnity extends third-party risk, procurement, and cybersecurity teams so they can cover their entire vendor portfolio. With ProcessUnity, organizations of all sizes reduce assessment work while improving quality, securing intellectual property and customer data so business operations continue to operate uninterrupted.