Skip to main content
CloudKey

CVE

Exploited Outlook and Cisco BroadWorks flaws: what to patch

CISA lists these Outlook and Cisco BroadWorks flaws as exploited. Check the affected products, verified fixed builds and component-specific upgrade guidance.

Conceptual illustration of two separate scenes: an email document being opened, and a server beside files and a shield

If you manage Outlook or Cisco BroadWorks, check affected installations and schedule the applicable vendor updates. CISA added CVE-2026-124194 and CVE-2026-20320 to its Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026, establishing known exploitation of both flaws.

For Outlook, match the Office release and update channel to Microsoft’s fix. For BroadWorks, identify the component before selecting Cisco’s fixed release.

Outlook: choose the fix for your Office release

CVE-2026-124194 involves a malicious message file opened by a user in vulnerable Outlook software. According to Microsoft’s Outlook security advisory, an attacker needs no prior authentication but must persuade the recipient to open the file. Outlook could then contact an attacker-controlled network location without its normal external-content warning, exposing authentication information.

Microsoft says exploitation needs both network connectivity and user interaction; the Preview Pane is not an attack vector. The relevant user action is opening the malicious file, not merely previewing a message.

Microsoft’s affected-product and update table gives these remediation paths:

  • Office Long Term Servicing Channel (LTSC) 2024: Microsoft lists fixed build 16.0.17932.21140.
  • Office LTSC 2021: Microsoft lists fixed build 16.0.14334.21048.
  • Microsoft 365 Apps for Enterprise: Microsoft directs administrators to security-release notes rather than specifying one fixed build. Use the guidance for the installation’s update channel.

Record the Office product, installed build and channel before deploying the update. The LTSC 2024 build is not the target for LTSC 2021, and neither LTSC build should be substituted for Microsoft 365 Apps channel guidance. After deployment, check the installed version against the applicable Microsoft update target.

Cisco BroadWorks: check the component and fixed release

CVE-2026-20320 concerns XML, a structured-data format used by the BroadWorks provisioning interface. The Cisco BroadWorks advisory describes a remote attacker who needs no authentication and can submit a malicious XML message to the Open Client Interface - Provisioning (OCI-P) service. The parser permits references to external resources, potentially letting the attacker read sensitive files using the BroadWorks user’s privileges.

Cisco identifies these products as affected when running vulnerable releases, regardless of device configuration:

  • BroadWorks Application Delivery Platform.
  • BroadWorks Application Server.
  • BroadWorks Profile Server.
  • BroadWorks Xtended Services Platform.

For each listed component, Cisco identifies releases before RI.2026.07 as affected and RI.2026.07 as the first fixed release. The Application Delivery Platform entry carries a footnote identifying Open Client Server (OCS) and OCIOverSoap; retain those details when matching the advisory to your inventory. Cisco reports no workaround that resolves the flaw.

Known exploitation here is attributed to CISA. In its November 13 correction, Cisco states: “Cisco does not have direct evidence of active exploitation.” The KEV listing supports prioritizing remediation, but it should not be described as independent Cisco confirmation or evidence of a newly observed campaign.

Why the scores should not delay remediation

The Common Vulnerability Scoring System (CVSS) describes technical severity. NVD records a Microsoft-supplied CVSS v3.1 base score of 6.5 for the Outlook flaw and a Cisco-supplied score of 7.5 for the BroadWorks flaw.

The Exploit Prediction Scoring System (EPSS) estimates the probability of exploitation in the next 30 days. FIRST’s dated observations for November 15, 2026 were 1.62% for CVE-2026-124194 and 0.976% for CVE-2026-20320. FIRST’s EPSS guide explains how to interpret this probability. The percentages here are the November 15 snapshot.

Use these scores as context, not as a reason to wait: CISA already lists both vulnerabilities as known to have been exploited. Prioritize the assets you actually run, using vendor applicability and fix guidance.

Verify the update on each affected asset

Keep the remediation record specific enough for another administrator to check:

  • Product or BroadWorks component, plus its installed build and Office update channel where applicable.
  • Applicable vendor fix, deployment owner and planned change.
  • Installed version observed after the update, checked against that fix.

A successful update addresses the vulnerability; it does not establish that the asset was never compromised. Keep patch verification separate from any investigation into earlier exposure.

Sources

Security research team

CloudKey Security Research

The CloudKey research team tracks emerging CVEs, exploit chains and active campaigns. Findings feed the platform and the customer advisories that follow.

Weekly brief

The 5-minute patch-priority brief

700+ CVEs drop every week. We send you the few that matter: what is exploited, what to patch first, what to skip.

No data resale. One-click unsubscribe, link in every email. Privacy.