CISA adds six exploited flaws: ask your providers for evidence
18 November 2026
This CISA KEV update gives Australian SMBs practical questions for phone, messaging and security providers, including what remediation evidence to request.
CISA’s 10 November 2026 announcement adds six vulnerabilities to its Known Exploited Vulnerabilities catalogue, citing evidence of exploitation. For Australian SMBs, this CISA KEV update is a reason to check both business devices and the infrastructure behind outsourced phone, messaging and security services.
The practical question is not simply whether you own a Cisco, Barracuda or Openwave product. It is whether an affected component supports a service you depend on, and whether the responsible provider can demonstrate that it has addressed the risk.
What the CISA KEV update covers
The announcement from the US Cybersecurity and Infrastructure Security Agency identifies these six entries:
| Vulnerability | Product or component identified | Where to start checking | | --- | --- | --- | | CVE-2026-20320 | Cisco BroadWorks; XML external entity handling | Hosted phone provider or underlying carrier | | CVE-2026-111560 | Multiple Barracuda products; operating system command injection | Security provider and appliance administrator | | CVE-2026-111793 | Openwave Messaging Webtop Media Transcoder; resource-boundary handling | Messaging provider or platform operator | | CVE-2026-116606 | Barracuda Email Security Gateway; authentication bypass | Email security provider or gateway administrator | | CVE-2026-124194 | Microsoft Office Outlook; unsafe action without required interaction | Endpoint and Microsoft 365 administrator | | CVE-2026-125350 | Google Chromium; use-after-free | Browser and application administrator |
These names are starting points, not a complete affected-version inventory. Confirm applicability, fixed releases and required recovery steps against the relevant vendor advisory. Do not assume every product from a named vendor is affected.
A KEV listing indicates exploitation has occurred somewhere. It does not establish that your business or provider has been compromised. Equally, having no visible disruption is not evidence that an exposed system is safe.
Map the service before asking about patches
An internal asset register may list handsets, laptops and a firewall but omit the platforms that deliver hosted services. A reseller’s brand can also differ from the underlying technology vendor.
Build a short service map with four fields: business service, contracted supplier, underlying operator where known, and the person responsible for obtaining security confirmation.
Start with these questions:
- Phone services: Does any part of our hosted calling service depend on Cisco BroadWorks? If so, has the operator assessed CVE-2026-20320 against the deployed components and versions?
- Messaging services: Is Openwave Webtop Media Transcoder used anywhere in our service delivery chain, and has CVE-2026-111793 been assessed?
- Security services: Which Barracuda products support our services? Have both listed Barracuda CVEs been checked separately against vendor guidance?
Do not accept “we do not sell that product” as a complete answer if the supplier relies on upstream infrastructure. Ask the supplier to obtain confirmation from its operator. Conversely, do not assume these components are present merely because a provider offers phone or email services.
Ask for evidence that matches your service
The strongest response to this CISA KEV update is a written, service-specific status report. “Our systems are updated” leaves too much unresolved: which systems, which vulnerability, and when?
Request the following:
- Applicability: The CVE, the relevant service and whether affected components are present. A “not affected” response should explain the basis, such as an unaffected version or absence of the component.
- Remediation: The applicable vendor advisory, the action taken, completion time and a change or support reference.
- Verification: Confirmation that the required fix or mitigation is active on all relevant instances, including standby or disaster recovery systems where applicable.
- Exposure: Whether the affected component was accessible through a vulnerable path before remediation, and the period assessed.
- Investigation: Whether checks for prior compromise were required or performed, what evidence was examined and any remaining limitations.
- Outstanding work: Temporary controls, unresolved actions, a responsible owner and the next update time.
Providers may reasonably withhold sensitive architecture or raw logs. A scoped attestation, redacted change record or technical summary can still provide useful evidence. The objective is accountable confirmation, not unnecessary access to another organisation’s infrastructure.
Separate remediation from compromise checks
Applying a fix and investigating earlier exploitation are different tasks. A successful update does not, by itself, establish that no attacker accessed the system beforehand.
Ask the responsible technical team to follow vendor-specific investigation and recovery instructions. Depending on the product and available evidence, checks may include unexpected administrative access, configuration changes, unfamiliar accounts, suspicious processes or unusual outbound connections. These are general investigation categories, not confirmed indicators for the six listed vulnerabilities.
Where credentials, sessions or connected services may have been exposed, ask whether further containment or credential changes are necessary under the incident response plan. Preserve relevant evidence before destructive changes wherever practical, while prioritising containment with the incident lead.
“No suspicious activity found” should state which logs were available and what period they covered. Missing logs create uncertainty; they do not prove a clean system. Our threat hunting checklist explains how to request investigation scope and findings rather than a simple reassurance.
Keep Outlook and Chromium in the response
The supplier focus should not obscure the two endpoint-related entries in the CISA KEV update. Assign the Outlook and Chromium checks to the team managing business devices and applications.
For Outlook, establish which installed products and builds fall within Microsoft’s advisory. Confirm deployment of the required update and any restart or application closure needed to complete it. A Microsoft 365 subscription alone does not confirm that every installed Outlook client is current.
For Chromium, check Google’s guidance and the advisories of relevant browser or application vendors. Do not assume every Chromium-based application is affected, or that updating one browser updates every embedded component.
Use management reports to identify missed devices, failed installations and exceptions. Give each exception an owner and a resolution date. This is also an opportunity to review broader Microsoft 365 hardening, without delaying the vulnerability-specific work.
Set priorities and protect service continuity
CISA’s federal directives apply to the specified US agencies; they do not automatically impose deadlines on Australian private businesses. Nevertheless, evidence of exploitation should move an applicable vulnerability ahead of routine maintenance work.
Prioritise confirmed affected systems using exposure, vendor guidance, business impact and available mitigations. Where provider confirmation is pending, record the status as unknown rather than unaffected, and set an escalation time.
Before changes to calling or email infrastructure, agree on:
- Expected interruption and the provider’s communication channel.
- Approved temporary workarounds if the service becomes unavailable.
- Post-change tests, such as inbound and outbound calling or email delivery.
- How to report faults without losing the security change record.
Keep rollback decisions aligned with security advice so that restoring service does not silently restore a vulnerable configuration. For communications planning, see our Microsoft 365 outage continuity checklist.
Close the action with a documented decision
Treat the CISA KEV update as an action register, not an email to forward and forget. For each relevant service, retain the applicability assessment, remediation evidence, investigation outcome, remaining limitations and business owner’s decision on unresolved risk.
Tech Engine can help you review your cyber security, coordinate questions with service providers and identify gaps in patching and investigation evidence. Call 1300 088 324 or email sales@techengine.au to discuss your services and responsibilities.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint