Facts are limited to what the linked sources support. Where a company or agency has not confirmed a claim, the item is marked unconfirmed.
01Confirmed#microsoft#entra-id#identity#phishing
Microsoft Entra Connect Health flaw was abused to read tenant admin data
Microsoft told affected customers that attackers exploited a flaw in the Entra Connect Health API and got read-only access to tenant metadata. The bug was introduced on 23 July and found on 9 November. Microsoft says the exposed data included administrator and technical-contact email addresses, tenant IDs, domain names, license tiers, directory sync status, Connect Health onboarding status, and an expired certificate that was no longer in use. It says passwords, hashes, tokens, valid keys, on-premises Active Directory layout and Azure subscription details were not exposed, and it found no unauthorized configuration changes. A server-side fix went out on 19 November and notifications followed. Microsoft has not said how many tenants were affected or who was behind it.
Why it matters
Leaked admin emails and tenant details are exactly what attackers need for convincing, targeted phishing against the people who hold the keys to your Microsoft 365 tenant. There is nothing to patch on your side; the risk is what happens next.
Who should act
Any organization using Entra Connect Health, especially MSPs that manage several tenants. Warn admins and the helpdesk about tailored phishing, require phishing-resistant MFA on privileged accounts, review Entra sign-in and audit logs, and run Microsoft's script at aka.ms/ConnectHealth/scripts to see which metadata types could have been exposed (it does not show what was actually accessed).
02Confirmed#microsoft#outlook#zero-day#patch-now#cisa-kev
Outlook zero-day CVE-2026-124194 leaks NTLM hashes; CISA deadline is 24 November
Microsoft's 10 November Patch Tuesday fixed CVE-2026-124194, an Outlook spoofing bug that is being exploited in the wild. If a user opens a crafted message file, Outlook can connect to an attacker-controlled network location without the usual external-content warning and leak the user's NTLMv2 hash, which can then be used to impersonate them. Microsoft says the Preview Pane is not an attack vector. Affected products include Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024; fixed builds include 16.0.14334.21048 and 16.0.17932.21140. CISA added the bug to its Known Exploited Vulnerabilities catalog and gave US federal agencies until 24 November to fix it. Microsoft has not said who exploited it or how widely.
Why it matters
A stolen NTLM hash can let an attacker sign in as the victim on other internal systems. Exploitation needs only one person to open one file.
Who should act
Anyone on Microsoft 365 Apps or Office LTSC: confirm Office is on a fixed build this week. IT teams should also consider blocking outbound SMB and NTLM to the internet and remind staff not to open unexpected message files.
03Confirmed#vmware#zero-day#patch-now#cisa-kev#virtualization
VMware vCenter authentication bypass exploited since September gets emergency patches
On 19 November Broadcom released emergency updates (VMSA-2026-0009) for CVE-2026-123890, a critical authentication bypass in the VMware Directory Service. An unauthenticated attacker with network access can gain access; Mandiant says successful exploitation creates an administrator@vsphere.local session. Google's Mandiant and threat intelligence team say a suspected China-linked group has exploited it since early September, after first breaking into BeyondTrust Remote Support appliances, then stealing directory data and forging SAML tokens. Broadcom listed no official workaround. CISA added the CVE to its exploited-vulnerabilities catalog on 20 November.
Why it matters
vCenter controls every virtual machine it manages. An attacker with admin there can reach the whole virtual estate, and this bug was used for about two months before a fix existed.
Who should act
Teams running vCenter, SDDC Manager or VMware Tools for Windows below the fixed versions: patch as an emergency, then check for signs of earlier compromise rather than assuming the patch closed the incident.
04Confirmed#cisco#patch-now#cisa-kev#edge-devices
Cisco Expressway critical bug CVE-2026-76466 is now exploited for root access
After a public proof-of-concept appeared, attackers exploited CVE-2026-76466 (CVSS 9.8) against Cisco Expressway devices at a Russian organization, according to The Hacker News. The flaw can let an unauthenticated remote attacker run operating-system commands as root. Cisco released patches on 21 October (X15.5.20 for the X15 branch; X14 and earlier must migrate). Russian security firm F6 said two internet-facing devices were compromised first, then two internal cluster nodes, after which the attackers scanned the network and accessed GitLab to steal credentials. The activity has not been tied to a named group. CISA added the CVE to its exploited-vulnerabilities catalog on 20 November.
Why it matters
Edge appliances like Expressway sit on the internet and inside the network at the same time. Once a public exploit exists, unpatched devices become an easy way in.
Who should act
Teams running Cisco Expressway, especially internet-facing or clustered appliances: confirm you are on a fixed release and check for the compromise signs F6 published.
05Confirmed#third-party-risk#data-breach#finance#phishing
Chase, Visa and Mastercard confirm incidents at third-party vendors
On 20 November J.P. Morgan Chase said attackers hit third parties that provide services to the bank and accessed some marketing data, which may include customer names and email addresses; its own services were not disrupted. Visa said the claims relate to a third-party provider in Asia Pacific and that its systems and card numbers were not affected. Mastercard said a provider exposed a limited number of email addresses for a small group of cardholders in one benefit program, and that the exposure is contained. The n0n ransomware group had claimed an October attack on cloud analytics firm Qubole and posted data it said came from those companies. Qubole had not commented, and the group's wider theft claims have not been independently confirmed.
Why it matters
No card numbers were reported stolen, but names and emails tied to a real bank or card relationship make phishing far more believable. It is also another case of a vendor's access becoming the customer's incident.
Who should act
Banks, fintechs and anyone who gives a vendor access into a cloud account should review those integrations and their permissions. Consumers should treat unexpected messages about their bank or card with extra care and contact the bank through its official app or number.
06Unconfirmed#government#data-breach#developing
FBI reportedly investigating an intrusion into the NCIC police database
AP and CNN, citing people briefed on the matter, reported on 21 November that the FBI is investigating an apparent intrusion into the National Crime Information Center (NCIC), the US system police use for warrants, missing persons, stolen vehicles, firearms and similar records. It is not publicly known when the intrusion happened, how access was gained, or whether any records were stolen or changed. The FBI has not publicly confirmed the incident. BleepingComputer notes there is no indication it is linked to earlier activity against FBIJobs.gov.
Why it matters
If confirmed, tampering with or theft from NCIC would be a serious integrity and privacy problem for US law enforcement. Scope and data theft are not established, so treat early claims with caution.
Who should act
No action for most organizations. US law-enforcement agencies should follow official FBI guidance. Everyone else: watch for confirmed details before drawing conclusions.
07Confirmed#msp#email-security#third-party-risk
N-able says a server breach, not a config issue, caused its Mail Assure outage
N-able first blamed the 16–17 November Mail Assure and SpamExperts Hosted Cloud outage on configuration and service dependencies. On 20 November it said the cause was a security incident: unauthorized access to one server in that hosted environment, affecting regions worldwide. The company said mail flow and spam filtering continued and that it had no evidence at that time of customer data or mailbox access. It took the management portal, quarantine, logging and mailbox-sync tools offline, so customers temporarily could not sign in, release quarantined mail or change domain settings. N-able said this is separate from an earlier N-central incident.
Why it matters
Email security platforms see every message a customer receives. A breach there, and a changing explanation from the vendor, is something MSPs need to track closely.
Who should act
MSPs and organizations using N-able Mail Assure or SpamExperts: follow vendor updates, rotate any credentials or API and OAuth tokens the vendor asks you to, and confirm portal access and quarantine handling are back to normal.
08Confirmed#cloud#kubernetes#credentials#secrets-rotation
Rackspace Spot accessed with leaked credentials; attackers could read Kubernetes Secrets
Rackspace told affected customers that on 17 November, between about 00:20 and 22:00 UTC, an unauthorized party used leaked credentials to access parts of Rackspace Spot, its Kubernetes cloud platform. The attacker could act as legitimate users in some customer organizations, create pods, read Kubernetes Secrets such as passwords, tokens and API keys, and list nodes and volumes. Rackspace learned of it on 18 November from a customer report. It says it revoked tokens and sessions, removed unauthorized pods, rotated keys and tightened access controls. The admin console was offline during cleanup and, per BleepingComputer, was fully restored on 21 November. Rackspace has not said how many customers were affected.
Why it matters
Kubernetes Secrets often hold the keys to databases, registries, Git and cloud storage. Anything stored there during the window should be treated as exposed.
Who should act
Rackspace Spot customers: reissue Spot API tokens, replace automation refresh tokens, download fresh kubeconfig files, rotate every credential stored in cluster Secrets, and review logs for connected services back to 17 November.
09Confirmed#third-party-risk#finance#data-breach#ireland
More than 40 Irish credit unions report a supplier breach, about six weeks late
Ireland's Data Protection Commission told The Record it had received more than 40 breach notifications from credit unions that use Belfast-based Wellington IT as a data processor. Ireland's minister said only payee details stored in Wellington-operated mobile banking apps were affected, with no evidence that members' funds were accessed or that fraudulent transactions occurred. The Irish League of Credit Unions said the attack happened in early October. Wellington closed an unidentified vulnerability on 6 October but did not initially identify a data breach, and credit unions were not told until 16 November. Wellington said it notified customers once it confirmed a potential risk to customer data.
Why it matters
A vendor fixing a vulnerability is not the same as a vendor investigating a breach. The gap here left customers unaware for about six weeks.
Who should act
Members who used the affected credit union apps should watch for misuse of payment details and for phishing. Organizations that rely on one processor for customer apps should set clear detection and notification terms in their contracts.
10Confirmed#ransomware#incident-response#law-enforcement
RansomwareHelp co-founder charged with wire fraud after an FBI sting
Krebs on Security reported on 20 November that the co-founder and CTO of ransomwarehelp.com was indicted in Rhode Island for wire fraud. The firm marketed proprietary cryptographic recovery and told victims not to pay ransoms. Prosecutors allege an FBI sting showed him instead buying a decryptor from what he believed was the ransomware group, then charging the supposed victim a markup for work that was not done. These are allegations; the case has not been tried. It follows other recent US prosecutions of ransomware recovery firms accused of secretly paying attackers.
Why it matters
Ransomware victims are under pressure and easy to mislead. A recovery firm that secretly pays the attackers can cost more and leaves the victim without control of the negotiation or the evidence.
Who should act
Organizations planning for ransomware: choose an incident-response firm before you need one, be wary of anyone promising guaranteed decryption, and keep control of negotiations and evidence.
How this briefing is made: Protego reads the original reporting and official advisories, writes a plain-English summary, and links every item to its sources. Claims a company or agency has not confirmed are labelled unconfirmed. Each day's briefing is reviewed before it is published. Spotted an error? Tell us.