Microsoft Patches Multiple Azure Vulnerabilities
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
NCSC-NL advisory lists 12 Microsoft Azure vulnerabilities, including a CVSS 10.0 flaw, affecting Key Vault, DevOps, API Center and Storage; no active exploitation reported.
NCSC-NL published an advisory summarizing vulnerabilities Microsoft has patched across several Azure components, including Key Vault, DevOps, API Center and Storage. The weaknesses span a range of classes: OS command injection, improper certificate validation, origin validation errors, missing authorization, server-side request forgery (SSRF), improper restriction of communication channels, and weak authentication. Successful exploitation could allow an attacker to bypass security controls, escalate privileges, execute arbitrary code, or access sensitive data.
Twelve CVEs are listed, with CVSS v3 scores provided for four of them: CVE-2026-96207 (10.0), CVE-2026-69435 (9.6), CVE-2026-83943 (8.7), and CVE-2026-83947 (7.7). Microsoft has already centrally remediated CVE-2026-83943, CVE-2026-96207, CVE-2026-69435, and CVE-2026-83947 server-side, so these require no customer action and are included for informational purposes only. The remaining CVEs require customers to apply updates made available by Microsoft.
No in-the-wild exploitation is indicated in this advisory. Defenders using affected Azure services should consult the Microsoft Security Response Center (MSRC) portal for per-CVE details, applicable updates, and any workarounds, and confirm whether their tenant configuration is affected given that some fixes are already applied centrally by Microsoft.
Mentioned in this report
Source reporting: https://advisories.ncsc.nl/2026/ncsc-2026-0421.html
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs