TL;DR: 16 November 2026 (2026-11-16)
- Exposed infrastructure comes first. Barracuda confirmed exploitation on 9 November. Check Point's November advisory describes exploitation followed by persistence. Treat patching and investigation as separate jobs. Barracuda advisory, Check Point advisory
- OpenSSH is a changed exploitation story, not a new disclosure. CISA added the musl-related issue on 9 November. Applicability still depends on the actual Linux, PAM and authentication configuration. CISA's 9 November bulletin, Alpine advisory
- Do not leave Outlook behind the highest CVSS scores. Microsoft confirms exploitation despite a 6.5 base score. Chrome's XML vulnerability also entered KEV. Microsoft, Chrome CNA and CISA enrichment
Get Cybersecurity updates in your inbox
Follow vulnerability reports, affected products, practical mitigations and links to the original advisories.
Select Cybersecurity in the free signup flow. Already a member? Sign in and update your email preferences. Unsubscribe anytime.
Overall overview
The retrieved CISA catalog is version 2026.11.13, released 13 November at 20:24:18 UTC. It contains 12 additions dated 9–16 November: four on the 9th, six on the 10th and two on the 13th. This calendar window includes 9 November and overlaps the date of the previous edition. The 12 additions are not 12 newly discovered vulnerabilities since that article. It is a specific snapshot, not complete visibility into every attack or disclosure. Official CISA catalog
My patch order starts with a question: can this asset expose a management plane, identity boundary or route into the rest of the environment? Then I consider observed exploitation and the consequences of failure. A medium-severity endpoint issue can deserve immediate deployment; a local flaw can become critical to an incident once another weakness provides entry.
EPSS estimates exploitation likelihood over the next 30 days across the observed population. It is not a probability that your own device is compromised, and its percentile is a ranking, not a second probability. The dated forecast does not overrule known exploitation. FIRST methodology and interpretation
At-a-glance priorities
The ordering is an editorial action sequence, not a claim that one deployment is universally more exposed than another. All scores below are FIRST's 16 November 2026 snapshot, retrieved on 17 November. Dated FIRST API response
| CVE and component | First action | EPSS probability | Percentile |
|---|---|---|---|
| CVE-2026-116606, Barracuda ESG | Verify exposure and applied security patch | 10.947% | 95.957th |
| CVE-2026-111560, Barracuda appliances | Match every affected product to its patch | 9.082% | 95.378th |
| CVE-2026-123039, Check Point Gaia | Deploy supported November JHF; investigate exposed gateways | 2.191% | 82.741st |
| CVE-2026-123158, OpenSSH/musl | Confirm applicability; patch and restart daemon | 18.900% | 97.341st |
| CVE-2026-124194, Microsoft Outlook | Deploy channel/product-specific Office security updates | 1.620% | 76.477th |
| CVE-2026-125350, Chrome XML | Update and relaunch; verify active browser build | 0.962% | 62.188th |
CVE-2026-116606 Barracuda ESG authorization bypass
| Field | Assessment |
|---|---|
| Affected versions | ESG before 9.4.0.030 in the Mandiant CNA record. |
| Severity | CNA: CVSS 4.0 9.3, Critical. Barracuda labels the same numeric score “High”; preserve the attribution rather than silently merging labels. |
| Vector | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| Prerequisites and impact | Reachable administrative interface; authentication is not required. Unauthorized appliance configuration changes are possible. |
| Exploitation | Barracuda's update at 21:00 EST on 9 November reports observed exploitation affecting a small number of organizations. |
| Fixes and remediation | Verify current firmware and the applicable ESG patch: BNSF-40425 for the vendor's 9.4.017+ branch notation, or BNSF-40430 below it. Confirm branch interpretation with Support if it differs from the displayed firmware. |
| Priority rationale | Urgent for reachable affected administration interfaces; patch receipt must be checked, not presumed. |
| EPSS | 16 November: 0.10947 probability, 0.95957 percentile. |
| Sources | CNA version and CVSS record, vendor patch/exploitation advisory |
What changes the decision: an “internal only” administrative interface and a publicly reachable one do not have the same exposure. Record the actual access boundary. Then obtain evidence that the security patch is installed on each appliance, not merely that an automated patching option is enabled.
Verification: retain the before-and-after firmware and patch identifiers, the exposure owner, and the investigation decision. If a device was reachable while vulnerable, route unexplained administrative or configuration changes to incident response. Do not close that investigation solely because the patch completed.
CVE-2026-111560 Barracuda appliance command injection
| Field | Assessment |
|---|---|
| Affected versions, CNA | ESG ≤9.4.0.27; ADC ≤6.4.0; WAF ≤11.0.1; WSG ≤16.1.100.100; Message Archiver ≤5.5.4.0; WAF Control Center ≤2.2.1. |
| Severity and vector | CNA: CVSS 4.0 8.6, High; CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. |
| Prerequisites and impact | Administrative access to the affected interface; command execution with root privileges. Do not describe this CVE alone as an unauthenticated flaw. |
| Exploitation | The vendor's 9 November update reports exploitation of the associated vulnerabilities; both entered KEV on 10 November. |
| Fixes and remediation | Vendor patches: ADC/WAF BNADC-16586; Message Archiver BNMA-32468; WAF Control Center BNWF-60060; WSG BNYF-24789. ESG uses the branch-specific patches above. |
| Priority rationale | Extend the inventory beyond ESG. A security fix for one product does not establish that related appliances are protected. |
| EPSS | 16 November: 0.09082 probability, 0.95378 percentile. |
| Sources | CNA affected-product matrix, Barracuda patch matrix |
The two Barracuda issues deserve separate inventory records even when they are handled in one maintenance window. One affects authorization in ESG; the other spans several product families. Combining them into a single “Barracuda patched” checkbox can conceal unremediated devices.
Verification: reconcile the asset list by product and patch identifier. Record unavailable or unsupported devices explicitly, with an exposure decision and owner. Do not infer a fixed build just by adding one to the affected version number.
CVE-2026-123039 Check Point Gaia privilege escalation
| Field | Assessment |
|---|---|
| Affected versions, CNA | Quantum Security Gateway and Security Management: R81.20 JHF Take 173 or below; R82 Take 130 or below; R82.10 Take 50 or below; R82.20 Take 10 or below. |
| Severity and vector | Check Point CNA: CVSS 3.1 7.8, High; CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. |
| Prerequisites and impact | An authenticated local foothold can be elevated to root. This is not itself the remote initial-access vulnerability. |
| Exploitation | Check Point describes actual exploitation alongside PHP2Shell. KEV addition: 13 November. |
| Verified fixed releases | Release notes dated 12 November explicitly list this fix in R81.20 Take 174, R82.10 Take 52 and R82.20 Take 14. The appropriate R82 fix was not independently verified here; obtain the supported take from Check Point. |
| Priority rationale | Internet-facing Mobile Access deployments deserve immediate exposure and incident review, alongside the supported November JHF rollout. |
| EPSS | 16 November: 0.02191 probability, 0.82741 percentile. |
| Sources | CNA scope/vector, vendor response guidance, R81.20 Take 174, R82.10 Take 52, R82.20 Take 14 |
What changed this week: the vendor's November reporting connects exploitation of the gateway with subsequent privilege escalation and persistence. Earlier PHP2Shell remediation does not automatically establish coverage of this separate local flaw. Conversely, fixing this local flaw does not substitute for closing the initial exposure. Check Point advisory
Verification: reconcile installed hotfix takes with each gateway and management server. For suspected compromise, coordinate evidence preservation and supported recovery with the response team before making disruptive changes. A clean version inventory is a remediation result, not an incident conclusion.
CVE-2026-123158 OpenSSH on musl
| Field | Assessment |
|---|---|
| Affected software | Portable OpenSSH before 10.6p2 on Linux using musl without PAM, subject to the account/authentication conditions in Alpine's advisory. Distribution backports can be fixed without changing to the upstream version. |
| Severity and vector | MITRE CNA: CVSS 3.1 8.1, High; CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. |
| Applicability | Verify libc, effective PAM use, password-authentication configuration and the account conditions. Do not mark every Linux host, or every container, affected merely because OpenSSH is installed. |
| Exploitation | Already covered in the 9 November edition. The retrieved official catalog now records a 9 November KEV addition; verify the listed exposure and fix status rather than treating this as a new disclosure. |
| Fixed Alpine packages | edge 10.6_p2-r0; 3.24 10.3_p1-r2; 3.23 10.2_p1-r1; 3.22 10.0_p1-r11; 3.21 9.9_p2-r1. Older supported-by-this-advisory backports are listed by Alpine. |
| Fixes and remediation | Install the relevant vendor fix and restart sshd. If changing authentication temporarily, verify working key access and recovery before the change. |
| Priority rationale | Urgent where the actual prerequisites and network reachability coincide. |
| EPSS | 16 November: 0.189 probability, 0.97341 percentile. |
| Sources | CNA score and scope, Alpine package and configuration guidance, 9 November CISA bulletin |
An upstream version comparison is not enough for a mixed fleet. Separate a glibc server from a musl-based container or appliance; then check the distribution's package revision. For a vendor-maintained appliance, use its support statement rather than replacing packages outside its update process.
Verification: the service must actually be running the fixed package. A completed package install with an old daemon still serving connections is an unfinished change. Include remote management continuity in the maintenance plan.
Keep track of what needs attention
Get the next security briefing with source-backed vulnerability context and clear distinctions between confirmed exploitation, exposure and mitigation.
Select Cybersecurity in the free signup flow. Already a member? Sign in and update your email preferences. Unsubscribe anytime.
CVE-2026-124194 Microsoft Outlook spoofing
| Field | Assessment |
|---|---|
| Affected products | Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024, including 32-bit and x64 deployments. |
| Verified fixed thresholds | CNA: LTSC 2021 16.0.14334.21048; LTSC 2024 16.0.17932.21140. Microsoft 365 uses a channel-dependent security-release reference, not one universal fixed build. |
| Severity and vector | Microsoft: base CVSS 3.1 6.5; vendor severity Moderate. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. |
| Prerequisites and impact | User interaction and network connectivity are required; Microsoft describes possible disclosure of authentication information. Its FAQ says the Preview Pane is not an attack vector. |
| Exploitation | Microsoft's 10 November release says exploitation was detected. |
| Fixes and remediation | Apply the security update for each Office product and deployment channel; verify the installed build. |
| Priority rationale | Confirmed exploitation and an identity consequence outweigh a simplistic “patch only critical scores” rule. |
| EPSS | 16 November: 0.0162 probability, 0.76477 percentile. |
| Sources | Microsoft advisory and FAQ, Microsoft CNA fixed thresholds, updated 16 November |
The deployment question is not simply whether “Office updates” ran. Mixed LTSC and subscription-channel estates can have different required builds. Ask for compliance by product and channel, plus the remaining exception list. A percentage across the whole estate can hide the cohort that matters.
Verification: confirm the version on the endpoint after the update process and required application restart. If suspicious authentication activity already exists, preserve it for identity-response review; the patch does not reverse credential exposure.
CVE-2026-125350 Chrome XML use-after-free
| Field | Assessment |
|---|---|
| Affected version | Google's CNA describes Chrome before 157.0.8103.50. |
| Severity and vector | Chromium severity High. CISA ADP, not Google's CNA, supplies CVSS 3.1 8.8, High and CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. |
| Impact | Code execution inside the browser sandbox. Do not relabel that as a demonstrated sandbox escape or full-host compromise. |
| Prerequisites | User interaction with malicious web content is required in CISA’s scored vector; verify exposed browser versions and complete relaunch. |
| Exploitation | KEV addition dated 10 November, recorded in CISA's enrichment. |
| Fixes and remediation | Install the supported Chrome update addressing the issue and relaunch. 157.0.8103.50 is the CNA threshold, not an independently verified threshold for every Chromium derivative or Extended Stable channel. |
| Priority rationale | Broad browser deployment makes rollout completion important even though this dated EPSS value is below 1%. |
| EPSS | 16 November: 0.00962 probability, 0.62188 percentile. |
| Source | Google CNA and CISA ADP record |
Verification: use the active browser build, not merely the downloaded installer or a pending-relaunch notification. Check other Chromium-based browsers against their own release advisories; a shared component does not make their release numbers interchangeable.
The Chrome release blog could not be retrieved reliably during this pass. The scope and threshold above therefore use Google's published CNA record, with CISA's scoring explicitly attributed. No Extended Stable build is guessed.
Other new KEV entries to match against inventory
These are additional entries in the same catalog window, not fully assessed version matrices in this edition. If a product is deployed, assign a vendor-advisory review rather than treating its absence from the six detailed sections as clearance. Official CISA catalog snapshot
| Product | CVE | Added |
|---|---|---|
| GPUStack | CVE-2026-102895 | 9 November |
| SignalWire FreeSWITCH | CVE-2026-116779 | 9 November |
| IBM Aspera Faspex | CVE-2026-123218 | 9 November |
| Cisco BroadWorks | CVE-2026-20320 | 10 November |
| Openwave Webtop Media Transcoder | CVE-2026-111793 | 10 November |
| UnrealIRCd | CVE-2026-114713 | 13 November |
What to finish this week
- Produce an exposure list, not just a CVE count. Record the reachable interface, asset owner, running version and supported fix.
- Separate patch evidence from compromise evidence. Close the maintenance task after deployment verification; close an investigation only when its own evidence supports that decision.
- Reconcile exceptions. Name the affected asset and owner, the temporary control, the reason patching is incomplete and the next review time.
- Verify running processes. Include the SSH daemon restart, Office build and browser relaunch in completion criteria.
Methodology and limits
The review is limited to the linked primary sources and does not assess a reader's own systems.
This edition uses the linked primary vendor, CNA and CISA records, checked on 17 November through the stated evidence cutoff. FIRST scores retain their 16 November snapshot date. Access limitations are identified in the relevant sections; no verification challenge was bypassed.
Reading a forwarded security report?
Get your own Cybersecurity briefing and choose the updates relevant to your work.
Select Cybersecurity in the free signup flow. Already a member? Sign in and update your email preferences. Unsubscribe anytime.