TL;DR · AI summary
Microsoft says attackers exploited a flaw in Entra Connect Health to read tenant metadata, and it fixed the flaw server-side. Rackspace says leaked credentials let intruders read Kubernetes Secrets on its Spot platform. The FBI is reportedly investigating an apparent breach of its NCIC criminal-justice database.
Today at a glance 5 stories · CISA KEV, NVD and source-reported status as of 2026-11-22
- Other stories 5no CVE from this briefing’s verified CVE table – status as the sources report it
- 1 Microsoft Entra Connect Health flaw exploited to read tenant metadata
- 2 Rackspace Spot breach exposed Kubernetes secrets in customer clusters
- 3 FBI reportedly investigating apparent hack of NCIC database
- 4 Two Norwegian energy companies report cyber incidents on consecutive days
- 5 Email bombing followed by fake IT-support contact on Microsoft Teams
Executive Summary
- Microsoft disclosed that attackers exploited a vulnerability in Entra Connect Health to read tenant-level metadata, including administrator email addresses; a server-side fix was deployed November 19.
- Rackspace told customers that an intruder used leaked credentials to access Rackspace Spot and could read Kubernetes Secrets in affected customers' clusters.
- The FBI is reportedly investigating an apparent hack of the National Crime Information Center (NCIC); the FBI has not publicly confirmed it.
- Equinor and Skagerak Energi, two Norwegian energy companies, reported cyber incidents on consecutive days; no link between them has been established.
- Fortra reports an email-bombing campaign followed by fake IT-support contact on Microsoft Teams.
Top Threats Today
1. Microsoft Entra Connect Health flaw exploited to read tenant metadata
Severity: MEDIUM Affected: Technology
Microsoft says attackers exploited a vulnerability in the Microsoft Entra Connect Health API to gain unauthorized read-only access to tenant-level metadata, according to a customer notification reported by BleepingComputer [1]. Microsoft found the flaw on November 9, 2026, and the notification says it was introduced on July 23 [1]. Exposed data includes tenant IDs, display names, initial domain names, country and region codes, license tiers, directory sync status and an expired Connect Health agent certificate [1]. Microsoft says no user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises topology or Azure subscription information were exposed, and it found no unauthorized configuration changes [1]. A server-side fix was deployed November 19, and no customer software update is required [1]. Microsoft has not said how many tenants were affected, who exploited the flaw, or when the attacks began; more than a dozen administrators reported receiving the notice on Reddit [1].
Sources:[1] BleepingComputer
Recommended Action
- Run the PowerShell script Microsoft published at aka.ms/ConnectHealth/scripts to see which tenant metadata types could have been exposed. It shows current configuration values, not what was actually accessed.
- Review Connect Health configurations and Microsoft Entra audit and sign-in logs for suspicious activity.
- Enforce phishing-resistant MFA on privileged accounts and warn security teams about targeted phishing aimed at the exposed administrator email addresses.
2. Rackspace Spot breach exposed Kubernetes secrets in customer clusters
Severity: MEDIUM Affected: Technology
Rackspace warned customers that an unauthorized party used leaked credentials to access its Rackspace Spot Kubernetes platform on November 17, 2026, between about 00:20 and 22:00 UTC, according to a notification obtained by BleepingComputer [1]. In some customer organizations the attackers could act as legitimate users, create pods, read Kubernetes Secrets and list nodes and volumes [1]. Rackspace said they could have read any Secret in an affected user's clusters, plus any Spot API or refresh tokens that user held [1]. Rackspace learned of the intrusion on November 18 from a customer report [1]. It says it revoked tokens and sessions, removed the unauthorized pods, rotated keys and tightened access controls and monitoring [1]. The incident caused an extended console outage, and service was fully restored November 21 [1]. Rackspace had not told BleepingComputer how many customers were affected or whether data was stolen [1].
Sources:[1] BleepingComputer
Recommended Action
- Reissue Spot API tokens, replace refresh tokens used in automation, and download fresh Kubernetes configuration files, as Rackspace instructed affected customers.
- Rotate every credential stored in cluster Secrets.
- Review logs for databases, container registries, Git repositories, cloud storage and third-party services back to November 17 for abuse of exposed credentials.
3. FBI reportedly investigating apparent hack of NCIC database
Severity: MEDIUM Affected: Government
The FBI is investigating an apparent hack of the National Crime Information Center (NCIC), the national criminal-justice database it maintains, according to a person familiar with the matter who spoke to the AP [1]. CNN first reported the incident, and BleepingComputer, citing CNN, says it was discovered in recent days [1][2]. NCIC is available to local, state and federal law enforcement and holds records on fugitives, missing persons, criminal history and stolen property [1]. The FBI declined to comment and has not publicly confirmed the incident [1][2]. BleepingComputer says it is unclear when the breach occurred, how the attackers got in, whether any information was stolen, or whether system availability was affected [2]. There is no indication it is tied to ShinyHunters’ earlier claimed compromise of FBI systems or to the recent government and private-sector outages [1][2].
Sources:[1] SecurityWeek[2] BleepingComputer
Recommended Action
- Agencies that use NCIC should watch for FBI or CJIS guidance; the sources report no confirmed scope or technical indicators yet.
- Treat the report as unconfirmed until the FBI issues a statement.
4. Two Norwegian energy companies report cyber incidents on consecutive days
Severity: MEDIUM Affected: Energy
Norwegian energy company Equinor says it stopped a cyberattack on some of its IT systems that it detected on November 17, according to SecurityWeek’s roundup [1]. Equinor said production was not affected, there is no sign data was stolen or altered, and the attack was not a virus attack and did not appear to be aimed specifically at it [1]. A day after Equinor’s disclosure, Norwegian power company Skagerak Energi reported activity that may have been an attempted cyberattack on some of its IT systems [1]. Skagerak said operations and production were not affected and there is no sign information leaked [1]. Dark Reading headlines the pair as two breaches in two days but notes that no specific link has been drawn between them [2].
Sources:[1] SecurityWeek[2] Dark Reading
Recommended Action
- Energy-sector defenders should watch for further disclosures; the sources give no indicators of compromise.
- Review IT-system monitoring and segmentation between IT and production environments.
5. Email bombing followed by fake IT-support contact on Microsoft Teams
Severity: MEDIUM Affected: Technology
Fortra Intelligence and Research Experts (FIRE) report attackers flooding employees with subscription emails and then contacting them on Microsoft Teams as supposed IT support offering to stop the messages [1]. Fortra says the instructions are intended to compromise the user’s account, system, or both [1]. The flood comes from “subscription bombing”, in which a target’s address is entered into newsletter and registration forms [1]. FIRE observed about 1,000 emails a day and up to 10,000 messages in an active campaign, with Mailchimp and Mandrill the most common platforms, followed by Amazon SES and SendGrid [1]. Evidence suggests attackers may use AI agents to find forms [1]. Fortra also saw phishing emails with fake loading screens during some attacks but could not conclude whether the same actors made the Teams calls [1]. In October, Hackread reported Arctic Wolf Labs research on over 400 similar fake-IT-support incidents via external Teams chats [1].
Sources:[1] HackRead
Recommended Action
- Review external access settings in Teams.
- Tell employees not to accept unexpected support calls and to contact IT through official channels.
- Preserve suspicious emails, and check account activity right away if an employee followed a caller’s instructions.
Today’s Action Checklist
- ☐ URGENT: Entra admins: review Connect Health configurations and Entra audit and sign-in logs, and enforce phishing-resistant MFA on privileged accounts.
- ☐ URGENT: Rackspace Spot customers: reissue API tokens, replace refresh tokens, download fresh kubeconfig files and rotate all credentials stored in cluster Secrets.
- ☐ Check logs for databases, registries, Git repositories and cloud storage back to November 17 for misuse of credentials that were in Kubernetes Secrets.
- ☐ Review Teams external-access settings and remind staff to verify unsolicited “IT support” contact through official channels.
- ☐ Monitor for official FBI statements on the reported NCIC incident.
Ongoing Coverage
CISA KEV watch from the CISA Known Exploited Vulnerabilities catalog as of 2026-11-22 · catalog data, not AI-written
Earlier additions with a federal deadline through 2026-11-29 (8)
CVE-2025-42884 SAP NetWeaver federal deadline 2026-11-23 (added 2026-11-20)
CVE-2026-123890 Broadcom VMware vCenter federal deadline 2026-11-23 (added 2026-11-20)
CVE-2026-129448 Apache Roller federal deadline 2026-11-23 (added 2026-11-20)
CVE-2026-76466 Cisco Expressway Series federal deadline 2026-11-23 (added 2026-11-20)
CVE-2026-111793 Openwave Messaging Limited Webtop Media Transcoder federal deadline 2026-11-24 (added 2026-11-10)
CVE-2026-124194 Microsoft Office federal deadline 2026-11-24 (added 2026-11-10)
CVE-2026-125350 Google Chromium federal deadline 2026-11-24 (added 2026-11-10)
CVE-2026-20320 Cisco BroadWorks federal deadline 2026-11-24 (added 2026-11-10)