A high-severity vulnerability in Microsoft Authenticator for Android let a malicious app with no Android permissions steal authentication tokens for a victim’s signed-in work account, potentially exposing Microsoft 365 email, files, calendars, and other enterprise resources.
Microsoft fixed the issue, tracked as CVE-2026-80097, in Authenticator version 6.2606.4246 and later.
Security researcher Ofek Levin, working through Enclave’s fellowship program, found that the weakness involved an exported Android activity, com.microsoft.identity.client.AccountChooserActivity.
Because the activity was exported, any app installed on the same Android device could invoke it. The attack required Microsoft Authenticator to be installed and contain an authenticated work account.
Microsoft Authenticator Flaw
The vulnerable component acted as a token broker for Microsoft applications. However, it accepted key identity fields directly from attacker-controlled intent extras, including the claimed package name, client ID, redirect URI, requested scopes, and caller UID.
The software could identify the genuine application invoking the activity through Android’s calling-activity mechanism, but it did not use that verified identity to make the authorization decision.
Instead, the validation routine evaluated whether the supplied redirect URI matched the signature-derived redirect URI for the package that the caller merely claimed to be.
This created a flawed trust model: an attacker could name a legitimate installed Microsoft application, retrieve its public package details and signature-derived redirect URI from the device, and submit matching values to satisfy the check.
In a proof of concept, researchers impersonated Microsoft Teams and requested Microsoft Graph permissions. The resulting delegated access tokens provided permissions including mailbox read and write access, mail sending, calendar access, file access, SharePoint access and Teams chat capabilities.
Ofek Levin also demonstrated that impersonating different Microsoft clients could return tokens with different scopes, including access related to authentication methods and passkey operations. The broker returned successful authentication results to the app that launched the activity.
According to the research, the response package could include access tokens, refresh tokens, ID tokens and client information in readable form, enabling the malicious app to use the victim’s Microsoft identity without requiring additional user interaction.
Microsoft assigned CVE-2026-80097 a CVSS score of 8.6, rated High, and classified it under CWE-287, Improper Authentication. The vulnerability was reported to the Microsoft Security Response Center and patched on September 8, 2026. Devices running versions prior to Microsoft Authenticator for Android 6.2606.4246 are affected.
Organizations should ensure managed Android devices receive the updated Authenticator release promptly, verify mobile application update compliance through endpoint management tools and investigate devices with suspicious Microsoft 365 token use.
Security teams should also treat unexpected delegated Graph activity, unusual refresh-token usage and account access from unfamiliar mobile clients as potential indicators of compromise.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team