<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>EntraID on Think Red</title><link>https://thinkred.dev/tags/entraid/</link><description>Recent content in EntraID on Think Red</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Nov 2026 08:12:35 -0500</lastBuildDate><atom:link href="https://thinkred.dev/tags/entraid/index.xml" rel="self" type="application/rss+xml"/><item><title>Entra Device Registration Elevation of Privilege Vulnerability</title><link>https://thinkred.dev/notes/entra-device-registration-elevation-of-privilege-vulnerability/</link><pubDate>Tue, 10 Nov 2026 08:12:35 -0500</pubDate><guid>https://thinkred.dev/notes/entra-device-registration-elevation-of-privilege-vulnerability/</guid><description>&lt;p&gt;Hello! I just noticed this recently vulnerability reported by Microsoft (&lt;a href="https://www.cve.org/CVERecord?id=CVE-2026-109469"&gt;CVE-2026-109469&lt;/a&gt;) on November 5, 2026. According to the description:&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&amp;ldquo;Authorization bypass through user-controlled key in Entra Device Registration allows an unauthorized attacker to elevate privileges over a network.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;This is not good. Any elevation of privilege may indicate the possibility of lateral movement. Why? Well all registered devices are &lt;em&gt;trusted&lt;/em&gt;. Meaning it has a Primary Refresh Token (PRT) and it behaves like a logged on device. So, if an attacker is capable of registering a fake device or hijacking one, it&amp;rsquo;s like a stolen credential. What this tells me is that attackers were likely able to register device linked to users that did not register the same device. This may even involve hybrid-joined device. Regardless, this appears to be the abuse. &lt;/p&gt;</description></item></channel></rss>