AuthMask
CVE-2026-80097, also called AuthMask, is an improper-authentication vulnerability in Microsoft Authenticator for Android versions earlier than 6.2606.4246. Its authentication broker accepts application-controlled identity fields without binding them to the actual calling application. The exported AccountChooserActivity validates signature-related redirect information against the installed application being impersonated rather than establishing the caller's identity and authorization. A malicious local application can consequently impersonate a trusted Microsoft application and receive work-account authentication tokens through an Android activity result. Microsoft classifies the issue as local privilege escalation with a CVSS score of 8.6.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises the confidentiality and integrity of resources accessible through the victim's signed-in work account. Researchers demonstrated Microsoft Graph access permitting reading and sending email, reading and modifying files and calendars, accessing SharePoint content, and sending Teams messages as the victim. Available access depends on the impersonated client, token scopes, and the user's existing permissions. Researchers also demonstrated impersonating Authenticator to modify account sign-in methods, including adding or deleting passkeys; an attacker-added passkey could preserve account access after removal of the malicious application. The vulnerability does not establish Android root access or arbitrary code execution.
If you can’t patch tonight, do this now.
Restrict sideloading and installation of untrusted applications, enforce enterprise mobile application controls, and use mobile threat detection to identify suspicious applications. Monitor Microsoft Entra ID sign-in events and Microsoft Graph activity for unexpected token use, unusual resource access, and changes to authentication methods. Correlate identity events with mobile endpoint telemetry. These measures reduce exposure or support detection but do not replace updating the vulnerable broker.
Patch, then assume compromise.
Update Microsoft Authenticator for Android to version 6.2606.4246 or later through Google Play. Enforce the minimum fixed version across managed devices using MDM or EMM and verify deployment. If exploitation is suspected, remove the malicious application, revoke affected users' sign-in sessions, investigate token and account activity, and review registered authentication methods for unauthorized additions. Whether updating Authenticator invalidates previously stolen tokens is not established.
1 exploit validated by Mallory's analysis.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
61 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.