Act this weekWhat happenedMicrosoft patched a flaw in Authenticator for Android that let a malicious app pretend to be a Microsoft app and collect work account access tokens.
Who is affectedAndroid users with Microsoft Authenticator and a signed-in work account, especially companies using Microsoft 365 on Android phones.
What to do- 1Open Google Play and update Microsoft Authenticator to version 6.2606.4246 or newer.
- 2Remove apps you do not recognize or did not get from Google Play.
- 3IT teams should check that managed phones run the current version and limit sideloaded apps.
- 4Watch for odd Microsoft 365 activity, such as sign-ins or file access from unfamiliar Android devices.
Microsoft has fixed a serious flaw in Authenticator for Android that let a malicious app pose as a Microsoft app and collect work account access tokens. The app needed no special permissions and no approval from the user. The bug is tracked as CVE-2026-80097 and scored 8.6 out of 10 for severity.
What happened
Authenticator acts as a go-between that hands out tokens. A token is a digital pass that proves you are signed in, so you do not have to enter your password each time. Researchers at Enclave found that a rogue app on the same phone could claim to be a trusted app, such as Microsoft Teams, and ask Authenticator for tokens in that app's name.
Authenticator checked whether the claimed identity looked valid. It did not confirm that the app asking was really that app. Because the real Teams app was installed, the fake request could pass the check. Authenticator then handed back the tokens.
Why it matters
Depending on which Microsoft app was imitated, the tokens could open Microsoft Graph, the service behind Microsoft 365 data. The researchers showed that a fake Teams identity could read and write mail, send messages, access files and change calendars. Mailboxes, OneDrive, SharePoint and Teams services could all be within reach.
Who it affects
The risk applied to Android phones with Microsoft Authenticator installed and a work account signed in. Companies that use Microsoft 365 on Android are the most exposed. The attacker needed a malicious app already installed on the phone, so this was not an attack that worked from afar.
Anyone who does not use Authenticator with a work account on Android was not in the situation described. Anyone running version 6.2606.4246 or newer has the fix.
What to do
Microsoft released the fix in July 2026. The steps in the alert box above cover the update and the cleanup for individuals and IT teams.
What happens next
The material does not say whether anyone used this flaw in real attacks. Microsoft's official advisory for CVE-2026-80097 is the place to look for ongoing guidance. Security teams are advised to keep watching for unusual Microsoft Graph activity, unexpected consent prompts and token use from unfamiliar Android devices.
The takeawayIf you use Microsoft 365 for work on Android, update Authenticator to version 6.2606.4246 or newer through Google Play.