
Microsoft Authenticator AuthMask Flaw Can Expose Android Tokens — Update Now
Microsoft has fixed CVE-2026-80097, an Important Microsoft Authenticator for Android elevation-of-privilege flaw with a CVSS 3.1 base score of 8.6.1 The minimum fixed build is 6.2606.4246; affected builds start at 6.0.0 and end before that version.2
UPDATE AVAILABLE • ANDROID ONLY • Reporting cutoff: October 27, 2026, 1:07 p.m. EDT
The bottom line
Update Microsoft Authenticator from the official Google Play listing, then verify the installed app version is 6.2606.4246 or later.24 The public Play page showed an October 26 update date at our cutoff but did not expose a current version number, so confirm the version on the device rather than assuming the store page proves it.4
Exactly who is exposed
This advisory is not about iOS. “Zero permissions” in the researcher’s title means the malicious Android app declared no Android permissions; it does not remove the requirement to get a local app installed and running.3
What AuthMask did
Researcher Ofek Levin of Enclave named the issue “AuthMask.” Enclave reports that an exported account-chooser activity trusted caller-supplied package, UID and redirect metadata instead of using the real caller identity for the trust decision.3 In Enclave’s tests, tokens were returned in plaintext and enabled delegated access to mailbox, files and calendar data; impersonating Authenticator itself exposed scopes for creating or deleting passkeys.3 Microsoft classifies the weakness as CWE-287, Improper Authentication.1
The primary sources disagree on user interaction
Microsoft says exploitation requires convincing the user to complete an Authenticator authentication flow.1 Enclave says its tests required no interaction beyond Authenticator already being present with one signed-in work account.3 We are preserving that discrepancy rather than treating either interaction model as settled.
What to do now
- Update first. Use the official Google Play listing and verify Microsoft Authenticator reports version 6.2606.4246 or later in Android app information.24
- If the update is not yet available, reduce risk while you wait. Avoid unexpected Authenticator flows, remove or quarantine untrusted apps, and restrict installs from unknown sources. Managed fleets can consider blocking outdated Authenticator builds, using managed work profiles and requiring compliant devices. This is practical risk reduction, not a vendor fix, and it does not fully remediate the flaw.
- If exposure is plausible, preserve evidence before destructive cleanup. After closing the vulnerable path with the update, retain device/app inventory and relevant timestamps before uninstalling apps or resetting the device. Review Microsoft Entra sign-in and audit logs, including authentication-method activity.6
- Contain confirmed or credible account compromise. Revoke the affected user’s sign-in sessions and refresh tokens as warranted; Microsoft notes that session revocation can take a few minutes and has limitations for external users.7 Remove unauthorized passkeys or other authentication methods from the user’s authentication methods.8
How to verify the fix
| Check | Pass condition | Important limit |
|---|---|---|
| Installed app | Microsoft Authenticator for Android is 6.2606.4246 or later.2 | The Play page’s update date is not version proof. |
| Device hygiene | No untrusted local apps remain; unknown-source installation is restricted where practical. | These steps reduce risk but do not replace the fixed build. |
| Identity review | Relevant sign-in, audit and authentication-method changes have been reviewed; suspicious sessions and methods are handled. | Absence of an obvious log entry is not proof that no token was exposed. |
Known-exploitation status
Microsoft’s advisory currently says the issue was not publicly disclosed before the patch, was not exploited, and was “Exploitation Less Likely.”1 CVE Program data carries a dated CISA enrichment value of “Exploitation: none” from September 9.2 CVE-2026-80097 was also absent from CISA’s Known Exploited Vulnerabilities catalog version 2026.10.26 available at our reporting cutoff.5 Those are point-in-time status signals, not proof that exploitation can never occur.
Sources
- Microsoft Authenticator Elevation of Privilege Vulnerability — Microsoft Security Response Center; released September 8 and revised September 15, 2026; rechecked October 27, 2026.
- CVE-2026-80097 record — CVE Program/Microsoft CNA; rechecked October 27, 2026.
- AuthMask: We Made Microsoft Authenticator Hand Over Tokens to an App With Zero Permissions — Ofek Levin, Enclave, October 23, 2026.
- Microsoft Authenticator on Google Play — official listing; rechecked October 27, 2026.
- Known Exploited Vulnerabilities Catalog — CISA, catalog version 2026.10.26 checked October 27, 2026.
- Microsoft Entra audit log activity reference — Microsoft Learn.
- Revoke a user’s sign-in sessions — Microsoft Graph documentation on Microsoft Learn.
- Manage and delete passkeys in Microsoft Entra ID — Microsoft Learn.
Source status: The live MSRC record, CVE Program record, researcher disclosure, official Play listing and CISA KEV feed were rechecked through October 27, 2026, 1:07 p.m. EDT. Microsoft’s September 15 revision corrected the fix build number; the fixed floor used here is 6.2606.4246.12
