• Nov 13

Microsoft Fixed a 10.0 Entra Bug. You Don't Need to Patch It.

Microsoft mitigated CVE-2026-109469. No customer action is required. Separate the cloud fix from sensible Entra device-registration checks.

A critical identity vulnerability with a perfect 10.0 severity score normally sends administrators looking for a patch. For CVE-2026-109469, that is the wrong response.

Microsoft says the Entra Device Registration vulnerability has already been fully mitigated. Its advisory states: “There is no action for users of this service to take.”

That is the headline small-business administrators need first—not an emergency checklist disguised as a fix. You do not need to change Conditional Access policies, delete devices, or install an update to address this CVE.

There is still value in understanding what Microsoft fixed and reviewing your own device-registration controls during normal maintenance. Those are two separate jobs. This guide explains the confirmed facts, the limits of the public disclosure, and a practical way to review your tenant without creating an avoidable outage.

What Microsoft actually disclosed

The MSRC advisory identifies Entra Device Registration Elevation of Privilege Vulnerability, CVE-2026-109469.

Microsoft describes it as:

Authorization bypass through user-controlled key in Entra Device Registration allows an unauthorized attacker to elevate privileges over a network.

The weakness classification is CWE-639: Authorization Bypass Through User-Controlled Key. Microsoft rates the vulnerability Critical, with a CVSS 3.1 base score of 10.0. The base vector is AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H: network attack vector, low complexity, no privileges or user interaction required, changed scope, and high confidentiality, integrity, and availability impacts.

Those are vulnerability-scoring characteristics, not evidence that every tenant was compromised. They do not identify the exact endpoint or privileges involved.

Microsoft's advisory release date is November 5, 2026, at 11:00 a.m. EST (America/Indianapolis). The Microsoft-authored CVE record was published on November 6 at 6:06 p.m. EST. These are disclosure timestamps, not a disclosed remediation timeline.

As checked on November 8, the advisory reports “Exploited: No,” “Publicly Disclosed: No,” and “Exploitation Less Likely.” Those are Microsoft's disclosure and exploitability assessments. “Publicly Disclosed: No” should not be read as saying the now-public advisory is secret. Nor should “Exploited: No” be expanded into an independent guarantee that no exploitation ever occurred.

Most importantly, the advisory's FAQ says:

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.

The official CVE record, supplied by Microsoft, corroborates the identifier, component, description, Critical rating, and base score. It carries the exclusively-hosted-service tag. It is corroboration of Microsoft's published account, not independent forensic evidence.

What the public advisory does not establish

The public text reviewed for this article does not disclose an affected endpoint, an exploit procedure, the exact privileges obtainable, or a tenant-by-tenant exposure assessment. It does not establish that tenant takeover occurred, that device-code phishing was the exploit path, or that requiring MFA would have prevented this flaw.

We should not fill those gaps with a plausible attack story. A vulnerability in a device-registration service is not evidence that every familiar device-registration attack technique applies to it.

Why a cloud CVE can have no customer patch

In its cloud-service CVE transparency explanation, MSRC says it issues CVEs for critical cloud-service vulnerabilities even when customers do not need to install a patch or take other protective action. Microsoft explains that the exclusively-hosted-service tag indicates no customer action is required.

The practical distinction is responsibility for the vulnerable component. A customer-managed server may need a customer-deployed update. A vulnerability in a provider-operated service may instead be resolved by that provider. You must read each advisory; “cloud” alone does not mean no action is ever needed.

For this advisory, Microsoft explicitly says mitigation is complete and users need take no action. A higher CVSS score does not override those instructions.

Illustrative example—not a reported incident: A 35-person consultancy asks its IT partner whether every laptop needs an emergency Entra patch. The partner records the advisory, Microsoft's mitigation statement, and the review date. It does not schedule a fleet-wide reinstall. It puts a separate device-policy review into the next maintenance window.

That is a proportionate response. If your tenant has independent evidence of compromise, investigate it through your normal incident-response process. This advisory neither proves compromise nor explains away suspicious activity you have actually observed.

First, separate registration, join, enrollment, and compliance

Before changing a device policy, make sure the business is talking about the right state.

Microsoft Entra registration creates a device identity associated with access to organizational resources. It commonly supports personal-device and mobile scenarios. A registered Windows device can still use local or personal credentials for device sign-in.

Microsoft Entra join is a different relationship with the organization, commonly used for organization-owned Windows computers. Microsoft Entra hybrid join combines an on-premises Active Directory relationship with an Entra device identity. The user-driven controls discussed below are not a blanket policy for every hybrid-join or userless provisioning scenario.

MDM enrollment brings a device under management through a service such as Microsoft Intune. Registration and enrollment can occur together in a workflow, but Microsoft explicitly states that registration is not enrollment.

Compliance is a separately evaluated state against configured requirements. A device appearing in Entra's directory is not automatically managed, compliant, healthy, or company-owned.

Similarly, MFA at registration supplies an authentication requirement for the user action. It does not inspect disk encryption, prove who owns the hardware, or certify that the endpoint is free of malware. Resource-access policies and management controls still have separate jobs.

Illustrative example: An employee registers a personal laptop to use a work application. The device appears in Entra, but it is not enrolled in your MDM. Calling it “trusted because it is registered” would turn an identity record into a security conclusion that the record does not support.

A general hygiene review—not remediation for this CVE

The following steps address ordinary tenant governance and authentication risks. Microsoft does not prescribe them as customer remediation for CVE-2026-109469. None establishes whether that vulnerability was exploited. The procedures below were checked against Microsoft documentation, not exercised in a live tenant.

Step 1: Establish permissions, licensing, and recovery first

For Conditional Access, verify Microsoft Entra ID P1 licensing for users benefiting from the policies. Microsoft lists Microsoft 365 Business Premium as including Conditional Access capabilities. Do not assume Business Basic or Business Standard includes the same entitlement. Intune and other connected products require their own appropriate licenses.

Use at least Conditional Access Administrator to create these policies. Microsoft's device-management documentation lists Cloud Device Administrator for reading and modifying device settings. Start log review with a suitable read-only role, rather than granting everyone a tenant-wide administrator role.

Before enforcement:

  1. Record current policy settings and exclusions.

  2. Confirm usable, secured emergency-access accounts and recovery procedures.

  3. Identify a pilot group and a maintenance window.

  4. Verify pilot users have a supported MFA method ready before device setup.

  5. Identify who can revert the change if setup fails.

Do not remove existing protection just to create a new policy. For an unlicensed tenant, first inventory current device settings and existing protections; do not disable security defaults merely to follow a Conditional Access walkthrough.

Step 2: Learn where device code flow is actually used

Device code flow lets someone complete authentication on another device when the initiating device has limited input. It has legitimate uses, but Microsoft also documents phishing risk and recommends blocking it wherever possible.

The name is easy to misread: device code flow is an authentication protocol, not a synonym for registering a device. Nothing in this CVE's public description establishes that this protocol caused the vulnerability.

Use Entra ID > Monitoring & health > Sign-in logs. Microsoft's authentication-flows guidance recommends filtering by Authentication protocol for device-code events. Review the associated account, application, resource, and business purpose. Look beyond one ordinary workday if equipment is provisioned infrequently.

Ask your support provider about command-line tooling, shared equipment, and conference-room devices. Microsoft specifically documents Teams-device scenarios that need carefully scoped exceptions.

Illustrative example: A small law firm sees little device-code usage until a meeting-room unit needs reauthentication. A blanket block without testing could leave the room unusable during a client meeting. Documenting the resource account and testing that lifecycle is better than discovering the dependency during an outage.

Step 3: Pilot a device-code block in report-only mode

Follow Microsoft's block authentication flows policy guide:

  1. Open Entra ID > Conditional Access > Policies and select New policy.

  2. Select the intended users. Plan toward broad coverage, excluding emergency-access accounts and only justified operational exceptions.

  3. Under Target resources > Resources, select the intended resources; Microsoft recommends All resources for the general block pattern.

  4. Under Conditions > Authentication Flows, set Configure to Yes and select Device code flow.

  5. Under Access controls > Grant, select Block access.

  6. Set Enable policy to Report-only and create the policy.

  7. Review the report-only results with the people responsible for affected workflows before enabling enforcement.

There is an important dependency: Microsoft's authentication-flows documentation says policies targeting all resources also enforce against Device Registration Service. If your organization uses device code flow for registration, follow its documented resource-exclusion guidance to avoid breaking that process. Microsoft's Teams-device guidance provides a more specific exception pattern for that use case. Do not add a broad exclusion simply because another organization needed it.

An exception trades coverage for functionality. Give it an owner, a documented purpose, and a review date. A different resource-access policy may still protect the excepted activity, but confirm that rather than assuming it.

Also account for protocol tracking: Microsoft documents that sessions originally established through device code flow can remain tracked through later refreshes. A subsequent blocked request might not look like a fresh device-code sign-in. Review Original transfer method when troubleshooting; a fresh authentication can be necessary after changing a policy back to disabled or report-only.

Report-only is an observation tool, not protection. Move to On only after validating real use, including infrequent provisioning and reauthentication.

Step 4: Require supported MFA for register-or-join actions

Microsoft recommends the Register or join devices Conditional Access user action for granular MFA enforcement. This is distinct from selecting Authentication context, which is used by supported applications and scenarios such as protected content or PIM activation. Creating an authentication context does not, by itself, protect device registration.

The device-registration policy guide documents this configuration:

  1. Create a policy in Entra ID > Conditional Access > Policies.

  2. Select the users in scope, preserving emergency-access exclusions.

  3. Under Target resources > User actions, select Register or join devices.

  4. Under Grant, choose Require authentication strength and the built-in Multifactor authentication strength.

  5. Validate with a small pilot before expanding enforcement.

There are prerequisites that matter more than the policy name:

  • Microsoft lists Require multifactor authentication and Require authentication strength as the supported grant controls for this user action. Other grant controls are unavailable.

  • Device-dependent conditions such as Filters for devices, Device state, and Client apps are unavailable for this action. Do not build a circular requirement that a new device already be compliant before it can register.

  • Microsoft says Windows Hello for Business and device-bound passkeys are not supported for this action, because they depend on an already-registered device. Ensure the onboarding user has a supported alternative.

  • If using external authentication methods, the guide currently instructs administrators to use Require multifactor authentication, rather than authentication strength.

  • The tenant-wide Require Multifactor Authentication to register or join devices with Microsoft Entra toggle must be No when using this user-action Conditional Access policy. Microsoft warns that otherwise these policies are not properly enforced. The documented location is Entra ID > Devices > Overview > Device Settings.

That last point needs a controlled transition. Do not turn the existing toggle off and leave only an untested or unenforced replacement. Plan the change, preserve recovery access, and test the effective MFA requirement on an actual supported registration or join.

Documentation caveat: Microsoft's specific device-registration guide suggests creating the policy in report-only mode. Its general report-only documentation, however, explicitly excludes policies in the User Actions scope from report-only evaluation. Do not treat an empty report-only view as proof this policy works. Use a tightly scoped, enabled pilot with a test user and a real registration/join, then expand only after validating successful MFA and recovery.

Test the process from a new device, not just an administrator's already-configured workstation. The tenant-wide MFA setting also has documented exceptions, including hybrid join, Entra-joined Azure VMs, and Autopilot self-deployment. Do not assume one switch governs every provisioning path.

Step 5: Review recent creation events alongside inventory

Use Entra ID > Devices > Overview, then inspect All devices. Review join type, owner, management state, compliance state, and activity information as separate attributes.

The same device-management guide places device Audit logs under the Devices page's Activity section. It documents device creation, owner/user additions, settings changes, updates, and deletions among the recorded activities.

Work through this sequence:

  1. Select an available recent date range and inspect device-creation activity.

  2. Open events and record the target identifiers, actor, result, timestamp, and correlation ID where available.

  3. Match the target to the device inventory and the employee or provisioning process expected to explain it.

  4. Compare relevant sign-ins around the event. Authentication evidence and directory-change evidence answer different questions.

  5. Review unexpected owner additions, device changes, and policy changes—not just creation.

  6. Preserve relevant records securely before making containment changes.

Do not mistake the audit actor for a human owner in every event: operations can involve services. Microsoft also notes that hybrid-joined devices may lack an owner, so search by device ID when an owner lookup fails.

There is no vulnerability-specific detection signature in the advisory reviewed here. This review identifies unexplained tenant activity; it is not a validated hunt for exploitation of this CVE.

Step 6: Investigate unknown devices before deleting them

An unfamiliar name is a lead, not a verdict. Compare device identifiers with the endpoint, your asset inventory, management records, deployment tickets, and a known-good contact with the employee.

Illustrative example: Two entries named after the same employee may represent different device relationships after reprovisioning. Conversely, a plausible company-style name does not make a device legitimate. Identifiers and corroborating events are more useful than naming conventions alone.

If evidence warrants containment, use your incident-response process and an appropriately authorized administrator. Microsoft documents that disabling a device prevents device authentication and revokes its Primary Refresh Token and refresh tokens. That can disrupt legitimate access and Windows Hello for Business; plan recovery. Do not assume it terminates every application's existing session or cleans an infected endpoint.

Deletion is not a harmless cleanup button. Microsoft calls it nonrecoverable and warns it removes attached information, including stored BitLocker keys. Managed devices require coordination with their management authority and the appropriate retirement or wipe procedure. Preserve needed recovery information securely and assess the impact before deletion.

Step 7: Make the review repeatable without overclaiming visibility

Microsoft's default Entra audit and sign-in retention is seven days for Free and 30 days for P1/P2. Upgrading does not recover expired data. Longer retention needs an appropriate supported retention or export arrangement, with its own access controls and potential storage or analytics costs.

For a small business, a recurring review with a named owner is more useful than an elaborate dashboard nobody checks. Record unexplained registrations, who investigated them, the outcome, approved device-code exceptions, and the next review date.

Missing history is a visibility limitation—not proof of compromise, and not proof that nothing happened.

Key takeaways

  • CVE-2026-109469 is real, Critical, and scored 10.0. Microsoft says it is fully mitigated and no customer action is required.

  • Treat Microsoft's exploitation fields as its reported assessment, not independent proof about every tenant.

  • Registration, join, MDM enrollment, and compliance are different states. MFA does not certify endpoint trust.

  • Device-code restrictions and registration MFA are general hygiene, not documented fixes for this CVE.

  • Pilot changes carefully. User-action report-only limitations, onboarding dependencies, and emergency recovery matter.

  • Investigate unexplained devices before deleting them. Preserve evidence and recovery information.

The sensible response is neither panic nor indifference: record the provider's completed mitigation, then manage your own tenant controls on their own merits.

Official sources

About IAMPathway

IAMPathway publishes practical guides on Identity & Access Management: Microsoft Entra ID, governance, identity threats, Application Governance and AI Governance. Browse all topics or read the glossary.