Microsoft Authenticator trusted the wrong Android app

Microsoft fixes Android Authenticator flaw that could expose work sign-in tokens

From the HARD Situation Room · First reported
msrc.microsoft.com: 🔃 Security Update Guide - Loading - Microsoft
Screenshot: msrc.microsoft.com

Enclave demonstrated token access using an app with no Android permissions. Microsoft says a sign-in step is required; the researchers report no further interaction in their tests.

What to do

  1. Update through Google Play.Open the Play Store yourself, find Microsoft Authenticator and tap Update if offered. Microsoft directs Android users to Google Play[5]; Google explains how to check for updates[6]. Install the latest available version, at least 6.2606.4246.
  2. Ask IT to confirm the version.If your employer manages the phone or its apps, ask them to confirm Authenticator meets that minimum. Include personal phones used for work in the check.
  3. Review your work sign-ins.Use Microsoft’s My Account portal to review recent activity. Check the app, browser and device details as well as location: mobile networks can make locations misleading. If you find a successful sign-in you did not authorise, change your password and contact IT. Microsoft’s sign-in review guide[7] explains what to look for.
  4. Escalate suspected access.Ask IT to investigate the phone and account and revoke sign-in sessions where appropriate. Do not assume an app update ends earlier access. Microsoft’s response guidance[8] explains that revoking access can take time and may require action in individual services.

What happened

If you use Microsoft Authenticator on an Android phone for work, install its latest update. Microsoft has fixed a flaw that could give a malicious app on the phone access to sign-in tokens. The fixed version is 6.2606.4246. Microsoft’s advisory[1] identifies the flaw as CVE-2026-80097.

A token is a digital pass an app uses to access services on your behalf. Getting hold of one can let an attacker act as you. Microsoft confirms that risk here[2].

Microsoft published its advisory on 8 September and corrected the fixed version number on 15 September. Enclave published its research on 23 October, followed by The Hacker News report on 27 October[3].

Microsoft Authenticator for AndroidCVE-2026-80097
Severity
High CVSS 8.6; Microsoft’s label is Important
Affected versions
Earlier than 6.2606.4246
Fixed version
6.2606.4246
Known exploitation
Microsoft’s advisory records none
What’s known.Microsoft’s advisory data and affected-version record[4].
The full story2 more sections

Who is affected

The demonstrated attack involved a work account signed into Authenticator on Android and a genuine Microsoft app, such as Teams, installed. Enclave’s test app needed no Android permissions: it impersonated the trusted app and received tokens giving access to work email, files and calendars. These were research tests. The Hacker News describes the findings[3].

Include any personal phone you use for work when checking updates. If you look after a parent’s phone and they use this setup, help them check theirs too.

Where the accounts differ

Enclave says its tests needed no further user interaction once the work account was signed in. Microsoft says[2] the attacker must also persuade the person to complete a sign-in process in Authenticator. The sources disagree. Update even if you remember no unexpected sign-in prompt.

The advisory does not say whether updating invalidates tokens already obtained. If you suspect unauthorised access, ask your IT team to investigate as well as confirming the update.

Timeline
  1. HARD publishes its article, at High.

References8
  1. ^ Microsoft Security Response Center (). “Microsoft Authenticator Elevation of Privilege Vulnerability”. Reader-facing advisory; substantive details verified through Microsoft’s API and VEX record below.
  2. ^ Microsoft Security Response Center (). “CVE-2026-80097 advisory data and FAQ”. Confirms Important severity, exploitation status, required sign-in interaction and potential token access.
  3. ^ The Hacker News (). “Microsoft Authenticator Flaw Let Permissionless Android Apps Steal Work Account Tokens”. Reports Enclave’s test results, publication date and disagreement with Microsoft.
  4. ^ Microsoft Security Response Center (). “CVE-2026-80097 affected and fixed versions”. Confirms affected Android versions, fixed build, CVSS score and advisory revision history.
  5. ^ Microsoft. “Download Microsoft Authenticator”. Directs Android users to Google Play for Authenticator.
  6. ^ Google. “How to update apps on Android”. Confirms how to find and install available app updates.
  7. ^ Microsoft. “View your work or school account sign-in activity from My Sign-ins”. Explains activity review, misleading mobile locations and password changes after unauthorised sign-ins.
  8. ^ Microsoft (). “Revoke user access in Microsoft Entra ID”. Explains tokens, administrator response, revocation delays and application-specific sessions.

Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.