Vulnerability mitigation in cloud and SaaS

In SaaS the vendor patches; the customer keeps data, endpoints, accounts, access and application configuration. In Microsoft's October 2026 release, 13 of 3,873 CVE records state that the issue was already fully mitigated and customers need take no action. For tenant settings, CISA BOD 25-01 made baselines mandatory for federal agencies by 20 Jun 2025.

  1. Remediate
  2. Mitigate now, fix laterThis page is about it
  3. Accept with a dated exception

What stays with the customer

Microsoft's shared responsibility page describes SaaS as "You use ready-made applications. Examples include Microsoft 365, Dynamics 365, and other cloud applications." It lists four responsibilities the customer "always" keeps: data, endpoints, accounts, and access management, including "role-based access control (RBAC), multifactor authentication, and conditional access policies". For applications: "In PaaS and SaaS, Microsoft manages parts of the application stack, but you're responsible for application configuration, code security, and access controls." For networks: "In SaaS, Microsoft manages network security."

When a SaaS flaw has no customer-side patch, those are the levers: who can reach the tenant, which accounts hold privilege and which features are on. The SaaS row of the decision table lists the duties by party. The controls themselves are described under access restriction and configuration change.

Five steps for a customer

Procedure written for this page from the sources listed; owners are illustrative.
StepWhoRecord it leavesHow it usually fails
1. Keep a list of the SaaS services in scope and the vendor's advisory feed for eachSecurity leadList with feed URL and a named readerScanners never see a vendor's own service, so with no watcher a cloud CVE reaches nobody
2. Read the vendor's customer-action field for each new recordVulnerability analystRegister line quoting the field and the dateClosing on the title alone. In Microsoft's October 2026 release the field reads Yes on 3,860 records, so the title cannot tell you
3. If no action: close with the vendor's statement. If action: apply the customer-side leverAnalyst, then identity or tenant administratorClosure quoting the statement; or a change ticket naming the settingCopying the vendor's word "mitigated" into the register as if it were your control
4. Compare tenant settings with a baselineTenant administratorAssessment output with dateRunning the tool once, not on a schedule
5. Put each deviation on the exception register with an approver and an end dateRisk ownerException lineDeviations tolerated with no end date

When the vendor has already fixed it: the 13 records

Microsoft's CVRF document for the October 2026 release (3,873 vulnerability records; document first released 13 Oct 2026, current revision 18 Nov 2026) holds 13 records with the FAQ: "This vulnerability has already been fully mitigated by Microsoft. There is no action for users of this service to take. The purpose of this CVE is to provide further transparency." Each of the 13 carries the field Customer Action Required: No and the exploitability line Exploited:No. They are the only records of the 3,873 with that field set to No; the other 3,860 read Yes. The release is large because 1,646 of those records list Azure Linux packages.

Microsoft MSRC CVRF API, October 2026 security updates, read 19 Nov 2026. CVSS values are the base scores in the records; the date is the Information published entry of each record's revision history.
CVEService and flaw typeCVSS 3.1 baseRecord published
CVE-2026-105014Azure Pipelines, remote code execution9.122 Oct 2026
CVE-2026-108456Azure AI Foundry, elevation of privilege7.722 Oct 2026
CVE-2026-110063VM Inspector for Azure Virtual Machines, elevation of privilege10.022 Oct 2026
CVE-2026-69435Azure SRE Agent, elevation of privilege9.68 Oct 2026
CVE-2026-77900Azure App Service, remote code execution9.88 Oct 2026
CVE-2026-83938Azure Kubernetes Configuration Service, elevation of privilege10.022 Oct 2026
CVE-2026-83943Azure API Center, information disclosure8.78 Oct 2026
CVE-2026-83947Azure Event Grid, spoofing7.78 Oct 2026
CVE-2026-88131Microsoft Dataverse, remote code execution9.88 Oct 2026
CVE-2026-94510Microsoft Bookings, elevation of privilege9.98 Oct 2026
CVE-2026-96185Microsoft Exchange Online, remote code execution7.522 Oct 2026
CVE-2026-96207Microsoft Partner Center, elevation of privilege10.08 Oct 2026
CVE-2026-97785AAD App Proxy, elevation of privilege10.022 Oct 2026

Cloud records are published on their own dates and are collected into the monthly document. Seven of the 13 carry a publication date of 8 Oct 2026 and six of 22 Oct 2026, so the dates fall before and after the document's 13 Oct release.

Several are rated 10.0 and none was exploited, which shows why the severity alone cannot set the customer's work: for these records the work is a closure with evidence. Note the vendors' own words differ. Microsoft says "mitigated" and does not say whether the flaw was eliminated or contained. Fortinet's FortiMail advisory FG-IR-26-175 says it "has remediated this issue" on 5 Oct 2026 in its cloud service. FedRAMP's rules keep the words apart: "A fully mitigated vulnerability will still exist (with negligible risk) until it has been remediated." That sentence is about a provider tracking its own service. A customer holds no control in these 13 cases, so no residual risk of the customer's own exists to track. Record the line as vendor-resolved, quote the vendor, and do not enter a customer mitigation that was never applied.

Register entry: vendor-resolved cloud vulnerability
  • Record: CVE-2026-96185, Microsoft Exchange Online, remote code execution, CVSS 3.1 base 7.5
  • Source: Microsoft MSRC CVRF, October 2026 release, first revision 22 Oct 2026
  • Vendor statement (quoted): "This vulnerability has already been fully mitigated by Microsoft. There is no action for users of this service to take."
  • Vendor fields: Customer Action Required: No. Exploited: No. Publicly Disclosed: No.
  • Our exposure: tenant uses Exchange Online (yes/no), checked by: [name], date: [date]
  • Customer-side control in play: none
  • Status: Closed, vendor-resolved, no customer action
  • Reviewer: [name], date: [date]
  • Reopen if: Microsoft revises the record, or the field Customer Action Required changes

When the customer must act: a record that reads Yes

Microsoft's October 2026 release also holds CVE-2026-100207, an OS command injection in Azure CycleCloud (CVSS 3.1 base 7.3, Important, first released 13 Oct 2026, Exploited: No, Publicly Disclosed: No). The record says Customer Action Required: Yes and lists CycleCloud 8.9.1 as affected with the security update 8.9.2. Microsoft's FAQ gives the conditions: the attacker must be authenticated to CycleCloud with permission to create or manage a cluster and to configure a Windows node's credentials, and a different user must then connect to that node with the CycleCloud CLI from a macOS or Linux workstation. The customer runs this software, so the vendor's fix does nothing until the customer installs it. Here the work is a version check, an upgrade and, until then, a look at who holds cluster-management permission.

Register entry: customer-action cloud vulnerability
  • Record: CVE-2026-100207, Azure CycleCloud, OS command injection, CVSS 3.1 base 7.3
  • Source: Microsoft MSRC CVRF, October 2026 release, first released 13 Oct 2026
  • Vendor fields: Customer Action Required: Yes. Exploited: No. Publicly Disclosed: No. Fixed in: 8.9.2
  • Our exposure: CycleCloud installed (yes/no), version [version], checked by: [name], date: [date]
  • Who holds permission to create or manage clusters: [list], reviewed by: [name], date: [date]
  • Customer-side control until upgraded: [none, or the permission change made]
  • Response: Remediate, upgrade to 8.9.2 by [date]; owner: [name]
  • Closure evidence: installed version after the upgrade, change ticket
  • Reopen if: a new revision of the record, or the entry appears on the KEV catalog

Configuration as a mandated mitigation

CISA's BOD 25-01 treats a configuration baseline as the control for SaaS. Its background says "Outdated security configurations expose systems to exploits that can be easily mitigated by recommended and mandatory security configurations." It covers production tenants with a finalized SCuBA Secure Configuration Baseline; at issuance only Microsoft Office 365 had one. Agencies had to deploy the assessment tools by 25 Apr 2025 and implement all mandatory policies by 20 Jun 2025. Authorizing officials "may accept risk for deviations from the mandatory SCuBA policies to account for operational needs", and agencies "shall identify and explain deviations in the output of the SCuBA assessment tools".

CISA describes ScubaGear as "a no-cost assessment tool that verifies M365 tenant configuration alignment to the policies described in SCuBA's secure configuration baselines", with ScubaGoggles as the Google Workspace counterpart. Both check a tenant you administer. A deviation is an exception in the sense of step five, so it goes on the exception register with the authorizing official as approver and an end date.

KEV wording for hosted products

In the KEV feed (catalogVersion 2026.11.18, read 19 Nov 2026), 329 entries carry the mitigate-or-discontinue string that tells readers to "follow applicable BOD 22-01 guidance for cloud services", and 11 more say "Adhere to the applicable BOD 22-01 guidance for cloud services". The 169 newest say "Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable". Counts by wording are on the KEV mitigate-or-discontinue guide. For a customer, discontinuing may mean switching off one integration rather than leaving the vendor.

Sources

Last reviewed