Cyber One Solutions logo.
Get Support

Security Advisory

This Week's Top 5: Fake Microsoft 365 Outage Notices, an Exploited VMware vCenter Bypass, and a Synology Flaw Back Under Attack

Published November 22, 2026 · Cyber One Solutions

Microsoft described a high-volume phishing campaign posing as Microsoft 365 service-health notices. CISA added a VMware vCenter authentication bypass and a 2024 Synology storage flaw to its exploited list, and vendors spent the week working out which products contain newly patched flaws in Java and the NGINX web server. Here are the five verified developments for small and mid-size businesses this week, ranked by relevance, exploitation evidence, and urgency.

This brief covers verified security and compliance developments from Sunday, November 15 through Saturday, November 21, 2026, with a research cutoff of Sunday, November 22, 2026 at 5:25 a.m. Central. It is the edition for the regular Sunday, November 22 slot. Last week was about patches for flaws already under attack. This week is more mixed: a phishing campaign aimed at Microsoft 365 users, two additions to CISA's Known Exploited Vulnerabilities (KEV) catalog that touch servers and storage many small businesses run in their own offices, and two flaws in widely shared software components where the work is finding out which of your products contain them. We found no new HIPAA, FTC Safeguards Rule, or CMMC development inside this window that we could confirm from a regulator's own publication.

Executive Summary and Priorities

Five verified developments met our bar for inclusion this week:

Only the second and third are confirmed as exploited. The first is an observed attack campaign, not a software flaw. The last two have public proof-of-concept code but no reported attacks as of our cutoff.

How We Ranked This Week's Developments

We ranked these five by how many of the businesses we serve use the affected technology, the strength and source of the evidence that attackers are active, what an attacker gains, and how soon action is needed. The phishing campaign ranks first because Microsoft 365 is so widely used for business email, Microsoft observed the campaign directly, and it works on any employee with an inbox. vCenter ranks second: fewer businesses run it, but for those that do, CISA lists the flaw as exploited, Broadcom scores it 9.8 with no workaround, and vCenter controls every virtual server beneath it. Synology ranks third because the flaw is confirmed exploited and these devices often hold a small office's backups, but the fix has been available since 2024. Java ranks fourth and NGINX fifth because neither has reported exploitation, both are hard to exploit by the vendors' own descriptions, and the affected-product lists are still being completed. These rankings are editorial judgments, not a measured risk score.

1. Phishing Emails Pose as Microsoft 365 Outage Notices

On November 16, 2026, Microsoft Threat Intelligence published an analysis of what it calls "a coordinated, high-volume phishing campaign targeting organizations across multiple sectors worldwide," observed on November 13. The emails were "disguised as legitimate Microsoft 365 service-health notifications" and claimed that "emails had been held during a service disruption and would be deleted within 24 hours unless the recipient took action to restore them."

Microsoft describes the pattern in detail. Subjects followed the form "Outage" plus a short random code. Display names combined a three-character prefix with "Outage Notification" or "Service Health." One example referenced a purported Exchange Online incident on November 12 and claimed four messages were being held. Buttons labeled "RESTORE MESSAGES" or "TAKE ACTION" led through tracking links to a website that does not belong to Microsoft.

Microsoft is careful about what it does not know, and so are we. It assesses the activity as "likely credential phishing," which means an attempt to capture a username and password, but says the available evidence "does not confirm credential capture, malware delivery, or post-compromise activity." It has not attributed the campaign to a named group. Microsoft also says Defender for Office 365 is blocking and quarantining these messages.

Who is affected: any organization that uses Microsoft 365 for email. Microsoft's blocking statement applies to environments protected by Defender for Office 365; it does not describe what other mail filters caught.

Why it matters: a stolen Microsoft 365 password is rarely the end of the story. Microsoft lists the risks that follow as "account compromise, mailbox access, business email compromise, internal phishing, inbox-rule manipulation, and access to cloud collaboration data." For a business that handles customer financial or health records, that mailbox may be where those records travel.

What to do this week: tell staff that Microsoft does not ask them to click a link to recover held mail. In Microsoft's words, "legitimate Microsoft 365 service-health communications do not direct them to non-Microsoft domains to recover held mail." Real service status is on the Service health page in the Microsoft 365 admin center, which your administrator or IT provider can check. If someone did click and enter a password, Microsoft's guidance is to reset the password, revoke active sessions, verify the account's multifactor authentication registrations, and review the mailbox for new inbox or forwarding rules.

2. A VMware vCenter Authentication Bypass Is Being Exploited

Broadcom published advisory VMSA-2026-0009 on November 19, 2026 and updated it on November 20. The most serious of its five flaws is CVE-2026-123890, an authentication bypass in the VMware Directory Service in vCenter. Broadcom scores it 9.8 out of 10 and states that "a malicious actor with network access to vCenter may exploit this issue to bypass authentication and gain unauthorized access to the system." The advisory lists no workaround.

vCenter is the management console for VMware virtual servers. A business that runs its file server, line-of-business application, and domain controller as virtual machines on VMware hosts usually manages all of them through vCenter, so access to vCenter is access to everything it manages.

CISA added CVE-2026-123890 to the KEV catalog on November 20, with a remediation due date of November 23. Broadcom's advisory does not itself say the flaw has been exploited; the exploitation evidence here is CISA's listing.

Who is affected, from Broadcom's response matrix: vCenter 8.0 before 8.0 U3m; vCenter in VMware Cloud Foundation and vSphere Foundation 9.0 before 9.0.2.0200 and 9.1 before 9.1.1.0200; and VMware Cloud Foundation 5.x before 5.2.5. For vCenter 7.0, the fixed version column reads "Contact Broadcom Support if you have extended support contract," which means there is no routine patch for that release. Businesses that do not run VMware on their own servers are not affected.

What to do: if your business has VMware hosts, ask whoever manages them which vCenter version is running and when the fixed version will be installed. Because there is no workaround, the patch is the fix. If you are still on vCenter 7.0, this is the week to ask about an upgrade plan. In either case, vCenter should be reachable only from the internal network used for administration.

3. CISA Adds a 2024 Synology Storage Flaw to Its Exploited List

CISA added CVE-2024-10441 to the KEV catalog on November 18, 2026, with a due date of November 21. The flaw is in Synology's DiskStation Manager (DSM), the software on Synology network-attached storage (NAS) devices, and in Synology's BeeStation OS. Synology rates it Critical with a score of 9.8, and its description says the flaw "allows remote attackers to execute arbitrary code."

This is not a new vulnerability. Synology's advisory, Synology-SA-24:20, was first published on November 5, 2024 and lists fixed releases: DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, and 7.1.1-42962-7 or above. The CVE record gives BeeStation OS 1.1-65374 as the fixed version. What changed this week is that CISA now has evidence the flaw is being used in attacks.

Who is affected: businesses with a Synology NAS that has not been updated since late 2024. A device that installs DSM updates as they are released is already past the fixed versions. Synology lists no mitigation other than updating.

Why a small business should care: a NAS in a small office is very often the place where backups land. An attacker who can run code on that device can read, alter, or delete what is stored there, and a backup that an attacker can delete is not much of a safety net. If you have a Synology device, check the DSM version the device reports against the list above, and ask whether the device's management page can be reached from the internet. The same event is a good prompt to confirm that at least one copy of your backups is kept somewhere the NAS itself cannot erase.

4. A Java Flaw With Public Exploit Code and No Reported Attacks

On November 17, 2026, the OpenJDK project and Oracle released fixes for CVE-2026-114938, a flaw in the Java runtime's HotSpot compiler, scored 8.1. Some vendors refer to it as "Java4Shell." Oracle's description calls it a "difficult to exploit vulnerability" that allows an "unauthenticated attacker with network access" to take over the affected Java software. OpenJDK's risk matrix lists Java versions 17, 21, 25, and 27 as affected.

Java is not something most small businesses think of themselves as running, but it sits inside many business applications and appliances, which is why three vendors we track published their own assessments this week. Cisco's advisory, first published November 18 and updated through November 20, says the flaw "affects OpenJDK Java 17.0.6 and later on x86-64 platforms when processing Base64 encoded content," that proof-of-concept exploit code is available, and that Cisco "is not aware of any malicious use." Fortinet's advisory FG-IR-26-278 lists "Known Exploited: No" and confirms FortiOS, the software on FortiGate firewalls, among the products not impacted, with a number of other products still under investigation. Palo Alto Networks says it "is not aware of any malicious exploitation of this issue" and lists fixes for a small set of its products. The flaw is not in CISA's KEV catalog.

Who is affected: applications and appliances that include an affected Java version and that process data from untrusted sources. Whether a given product qualifies is the vendor's call to make, and several of those lists are unfinished.

What to do: nothing urgent on your own. Ask your IT provider or software vendors whether the business applications you rely on, such as accounting, document management, or practice management software that runs on a server in your office, bundle Java, and whether an update is planned. This belongs in the next maintenance cycle unless the exploitation picture changes.

5. NGINX Fixes Reach Firewalls and Other Appliances

NGINX is one of the most widely used web servers, and it is also built into many network products to run their web interfaces. On November 18, 2026, the NGINX project released versions 1.31.9 and 1.30.7 with fixes for a batch of security flaws. Two of them, CVE-2026-123007 and CVE-2026-123633, are in the way NGINX handles HTTP/2, the protocol most modern websites use. The CVE records, published by F5, which maintains NGINX, say each can crash an NGINX worker process and that "attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR." ASLR is a standard memory protection that is on by default in modern operating systems, which is why both are rated as difficult to exploit.

The practical question is which products contain an affected NGINX. Palo Alto Networks answered for its firewalls on November 20: PAN-OS and Panorama are affected only where the HTTP/2 option is enabled, with fixes in PAN-OS 12.2.4-h3, 12.1.10-h6, and 11.2.16-h3 and later, among other fixed builds listed in its notice. It also notes that customers can disable the HTTP/2 option as a workaround, which is a decision for whoever administers the firewall. Cisco says proof-of-concept code is available and that it is not aware of malicious use; its Secure Firewall ASA and Threat Defense software are listed as not affected, while other products remain under investigation. Fortinet's FG-IR-26-279 lists "Known Exploited: No" and confirms FortiOS as not impacted.

Who is affected: businesses with a Palo Alto Networks firewall that has HTTP/2 enabled, businesses that run their own NGINX web server, and customers of other products still being assessed. A website hosted with a managed provider depends on that provider's patching, which is a fair question to ask them.

What to do: plan the firmware update if you have an affected Palo Alto Networks firewall, and ask your website host whether its NGINX servers have been updated to the November 18 releases.

Also Added to the KEV Catalog This Week

CISA added nine entries between November 17 and November 20. Beyond the two ranked above, one is worth a mention for businesses with on-premises Cisco collaboration and video conferencing gateways: CVE-2026-76466, in Cisco Expressway Series, added November 20 with a due date of November 23. Cisco's advisory, published October 21, says the flaw affects Expressway-C and Expressway-E devices that are configured in a cluster, and that it is fixed in release X15.5.20. Cisco's advisory has not been revised to report attacks, so the exploitation evidence is CISA's listing.

Medical practices and research groups should also know that CISA added CVE-2026-90817, a code injection flaw in REDCap, the survey and data capture software from Vanderbilt University that many health research teams use. If your organization hosts its own REDCap server, ask its administrator about the vendor's fix.

The remaining additions, in Apache Roller, Apache Axis, SAP NetWeaver, BerriAI LiteLLM, and Perforce Puppet Enterprise, are not products a typical small business runs itself.

Updates on Earlier Items

The federal due date for two flaws we ranked first and second last week, the Outlook flaw CVE-2026-124194 and the Chromium flaw CVE-2026-125350, is Tuesday, November 24. Microsoft's November release data, checked at its November 21 revision, still marks the Outlook flaw as the only exploited vulnerability in the release.

Browsers moved on to a new major version. Google promoted Chrome 158 to the stable channel on November 17 (158.0.8127.36 for Linux and 158.0.8127.36/.37 for Windows and Mac) with 204 security fixes and no statement that any of them is being exploited. Microsoft released Edge Stable 158.0.4370.33 on November 19. Both install on their own and take effect when the browser is restarted.

SonicWall published no new advisory this week. CISA's due date for the SonicOS SSL VPN bypass, CVE-2026-19868, passed on November 20.

Do Now

Plan Next

Watch List

The Bottom Line

The two confirmed-exploited items this week sit in server rooms and storage closets, not on desktops, and the lead item needs no software flaw at all. CISA's due dates bind U.S. federal civilian agencies, not private businesses, but they are a reasonable benchmark for how quickly the exploited items should be handled. This brief is general security awareness, not a HIPAA, FTC Safeguards, or cyber-insurance compliance service. Cyber One Solutions manages Microsoft 365 tenants, including the sign-in and mail protection settings that limit what a phished password can do, through our Microsoft 365 support service, and designs and monitors backups for servers and storage through backup and disaster recovery. If this week's storage and virtualization items left you unsure whether your backups would survive an attack on the systems that hold them, our backup and disaster recovery readiness self-assessment is a good place to start.

Sources