Zero Day Room
Live
Vulnerabilities

Microsoft patches critical Android Authenticator flaw allowing token theft

A high-severity vulnerability in Microsoft Authenticator for Android allowed malicious apps to silently steal work account tokens.

A high-severity vulnerability in Microsoft Authenticator for Android allowed malicious apps to silently steal work...

A critical vulnerability in Microsoft Authenticator for Android allowed malicious apps to steal authentication tokens without any user approval. The flaw, tracked as CVE-2026-80097, impacted devices running versions before 6.2606.4246 and has been patched.

Any app installed on the same Android device could exploit this flaw to silently steal access. The attack required Microsoft Authenticator to be installed and contain a signed-in work account. No user interaction, account credentials, or special Android permissions were needed beyond the malicious app's installation.

Successful exploitation granted attackers extensive access to corporate data. The stolen delegated access tokens could provide capabilities across Microsoft Graph resources.

An attacker could even add a malicious passkey to maintain persistent access after the rogue app was removed. This made the flaw especially dangerous for organizations using Android devices to access Microsoft 365 workloads.

Technical Breakdown of the Exploit

The flaw stemmed from improper validation of the calling application's identity. Security researchers at Enclave discovered the issue originated from an exported Android activity called com.microsoft.identity.client.AccountChooserActivity. This component acted as a token broker for Microsoft applications.

Authenticator verified the requesting application's claimed package name and redirect URI but failed to confirm the real caller's identity. Attackers could supply valid redirect URIs matching a legitimate installed Microsoft app's public package signature to pass validation. Although Authenticator could identify the real caller via Android's getCallingActivity() mechanism, it did not use this information in security decisions.

The vulnerable workflow trusted identity details supplied by the requesting app itself. Researchers demonstrated impersonation of multiple trusted Microsoft clients, like Teams, to request and receive tokens. The proof of concept showed successful authentication results, including access tokens, refresh tokens, ID tokens, and client information, returned directly to the malicious app that launched the activity.

Impact on Organizations and Users

The vulnerability specifically impacts Android devices with Microsoft Authenticator installed and signed-in work accounts. It enabled silent theft of email, files, calendar, SharePoint data, and Teams messages. The impact could extend to any Microsoft Graph resource accessible via delegated tokens.

Microsoft classified the issue as a local elevation-of-privilege flaw under CWE-287, Improper Authentication. They assigned it a CVSS score of 8.6, rating it High severity. The vulnerability highlighted a critical need for mobile identity brokers to validate the real calling application identity via package identity, UID, and signing certificate.

Microsoft's Response and Mitigation

Microsoft confirmed the report and issued a fix. The company released version 6.2606.4246 in July 2026 and published the official vulnerability advisory on September 8, 2026. Organizations and individual users must update the app through Google Play immediately.

Managed devices should run this current release. Organizations should enforce the updated version through Mobile Device Management (MDM) or Enterprise Mobility Management (EMM) policies. They must also verify mobile application update compliance through endpoint management tools.

Microsoft's ongoing work includes protecting Entra credentials on rooted Android and jailbroken iOS devices. The company's official CVE-2026-80097 advisory provides detailed remediation guidance.

Mobile threat detection teams should monitor managed Android devices for indicators of compromise. These include unexpected delegated Microsoft Graph activity, unusual refresh-token usage, and account access from unfamiliar mobile clients. Organizations should treat such signs as potential compromise indicators and investigate devices with suspicious Microsoft 365 token use.

Users should avoid sideloading apps or installing unfamiliar software from untrusted sources. Organizations should review mobile application controls and restrict sideloaded apps where possible. The report also mentions integrating threat intelligence feeds with data from thousands of security operations centers to update defenses against new malware.

Organizations should enforce the updated Authenticator version through MDM policies and users should update the app immediately via Google Play.

Related coverage

More from Vulnerabilities