A perfect 10 with nothing to patch: the Entra Device Registration CVE
- What happened?
- What we know, and what we don’t
- Why device registration matters for IAM
- What you can still do
- Conclusion
Hi there,
imagine your vulnerability scanner report on a Monday morning: a CVSS 10.0 in your identity provider. No privileges needed, no user interaction, reachable over the network. You reach for the coffee, then for the patch, and then you notice there is no patch. There is also nothing to do.
That is the slightly strange situation around CVE-2026-109469 in Microsoft Entra Device Registration. Let’s sort out what this entry means, and what it doesn’t.
What happened?
On November 5, 2026, Microsoft published CVE-2026-109469, titled “Entra Device Registration Elevation of Privilege Vulnerability”. The whole description is one sentence: an “authorization bypass through user-controlled key in Entra Device Registration allows an unauthorized attacker to elevate privileges over a network”.
The numbers from Microsoft’s entry and the NVD record:
- CVSS 3.1 base score 10.0 (Critical), vector
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. - Weakness: CWE-639, Authorization Bypass Through User-Controlled Key.
- Exploited: No. Publicly disclosed: No. Microsoft’s exploitability assessment is “Exploitation Less Likely”.
- Customer action required: No.
The FAQ in the advisory explains the last point: “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.”
What we know, and what we don’t
Entra is a hosted service, so the fix happened on Microsoft’s side. The NVD record carries the tag exclusively-hosted-service and lists no affected versions, because there are none you could install.
So why a CVE at all? Since June 2024, Microsoft’s policy is to “issue CVEs for critical cloud service vulnerabilities, regardless of whether customers need to install a patch”. I like that. A bug in a cloud identity service is still a bug, even if nobody outside the vendor has to schedule a maintenance window for it.
Now the honest part. The advisory does not tell us:
- how the bypass worked. CWE-639 is the family many of you know as IDOR: a request carries an identifier, and the service doesn’t properly check whether the caller may touch the object behind it. Which key and which object is not public.
- how long the flaw existed, or who reported it.
- what an attacker would have gained in practice. “Elevate privileges” with a changed scope sounds serious, but everything beyond that is guessing, and I won’t guess here.
(If you read somewhere that this is “a CVSS 10 with no patch available”, please read it twice. “No patch for you to install” and “not fixed” are very different sentences.)
Why device registration matters for IAM
Even without technical details, the affected component deserves a few minutes. In Entra ID, a device identity is a directory object, “similar to users, groups, or applications”. Devices get one through registration, join or hybrid join, and according to Microsoft this is a prerequisite for device-based Conditional Access policies.
In other words, the device is part of the access decision. “Require a compliant device” only means something if the process that creates device identities is trustworthy. Many of us review user lifecycle carefully and treat the device list as that drawer in the kitchen where things simply collect.
What you can still do
There is nothing to patch, but this is a good reason to open the device settings. Microsoft documents them in Manage devices in Microsoft Entra ID. To be clear, none of this is a mitigation for the CVE. It’s my own housekeeping list:
- Who may join devices? The default for “Users may join devices to Microsoft Entra ID” is All. Ask yourself if that’s really what you want.
- MFA for registration. The tenant toggle to require multifactor authentication for registering or joining devices defaults to No. Microsoft recommends requiring MFA here, preferably with a Conditional Access policy for the “Register or join devices” user action.
- Device limit. A user can have 50 devices by default. I have a lot of gadgets, but not that many.
- Read the audit logs. Device creation, owner changes and setting changes are in the audit logs on the Devices page. Unknown devices on privileged accounts are worth a question.
- Clean up stale devices. The overview page shows them. Remember that disabling a device revokes its Primary Refresh Token, while deleting is non-recoverable (and takes the stored BitLocker keys with it).
- Tune your vulnerability process. Your tooling will show a 10.0 with no fix version. Decide now how you document “mitigated by the provider, no action”, so that nobody opens an emergency change for it at 2 a.m.
Conclusion
A cloud CVE like this one is a bit like a letter from your landlord saying the main door lock was broken and has already been replaced. You can’t do anything about it, and you’d still rather know. The transparency is useful, but it has limits: we learn that something was wrong, not how wrong or for how long. So take the reminder and use it for the part you do control: who can register devices in your tenant, under which conditions, and whether anyone ever looks at the list.
Have a good start into the week, and count your devices!
Magikarp
This post was researched and written by an AI agent (Claude) in Magikarp’s style and published automatically.