Microsoft Authenticator Flaw Let Fake Apps Steal Work Logins
A security flaw in Microsoft Authenticator for Android let a malicious app pose as Microsoft Teams and walk away with a live sign-in token for a victim’s work account — enough to read and send email, open files, and view calendars, all from an app that asked for zero device permissions. Microsoft has fixed the bug, tracked as CVE-2026-80097 and rated 8.6 out of 10 (“Important”) on the industry’s severity scale. If your business runs Microsoft 365 and your team uses Authenticator to sign in on Android phones, this is worth five minutes of your time today.
What happened
Most people think of Microsoft Authenticator as a one-trick app: it shows a six-digit code or sends a push notification when you log in somewhere. On Android, it actually does more than that. When an app like Teams or Outlook needs to confirm you’re signed into your Microsoft work account, it can quietly ask Authenticator to vouch for you, and Authenticator hands back a token — a kind of digital pass — proving you’re logged in.
Security researcher Ofek Levin, working through a fellowship with the research firm Enclave, found that Authenticator exposed a component called AccountChooserActivity that any app installed on the phone could trigger — no special permissions required. Worse, when Authenticator built the token request, it used whatever identity the calling app claimed for itself. A malicious app could simply say “I’m Teams,” and Authenticator would start building a Teams-flavored request.
There was supposed to be a safeguard: a signature check meant to confirm the request was really coming from Teams. But Enclave found that check only confirmed the real Teams app’s signature existed somewhere on the phone — not that the app actually making the request was Teams. If the real Teams app happened to be installed too (which, for a work phone, it usually is), the check passed regardless of who was really asking.
In testing, posing as Teams and requesting a Microsoft Graph token this way returned permissions to read and send mail, read and write files, and read and write calendar entries — in other words, the keys to someone’s entire Microsoft 365 work account. Microsoft reports that triggering the bug also requires the victim to complete a sign-in step inside Authenticator, so it isn’t a silent, zero-click takeover; but the malicious app itself needed no permissions at all to start the process, which is what makes it easy to sneak past anyone who checks an app’s permission list before installing it.
Why it matters to a business like yours
If your company uses Microsoft 365 — email, SharePoint, Teams, the calendar most of your staff lives in — Authenticator on employees’ Android phones is almost certainly the gatekeeper standing between a stranger and that account. This flaw mattered because it undercut the thing a password manager or multi-factor authentication is supposed to guarantee: that logging in on a phone actually means you, and only you, get the access.
Three things are worth sitting with:
- No unusual permissions needed. The attacking app didn’t need camera access, contacts, storage, or anything else that would normally raise a red flag during install.
- Full mailbox and file access. This wasn’t a narrow leak — a stolen token could cover email, OneDrive/SharePoint files, and calendar data in one shot.
- It rode on trust you already have. The attack worked precisely because Teams was a real, trusted app on the device. Employees weren’t tricked into installing something obviously fake-looking as “Teams” — the malicious app just claimed to be Teams behind the scenes.
Microsoft says it has not seen this flaw used in real-world attacks, and that exploiting it required a victim to complete a sign-in step in Authenticator — so this is a disclosed-and-fixed risk, not an active campaign you need to hunt for signs of. The right response is prevention, not incident response.
What to do about it
Microsoft fixed the underlying signature-check logic in Microsoft Authenticator for Android version 6.2606.4246. The fix is already out — the only step left is making sure every phone in your business has it.
- Open the Google Play Store on each work Android phone, search “Microsoft Authenticator,” and tap Update if one is available. Most phones with auto-update on will already be current.
- To check the exact version, open Authenticator, go to Settings → About, and confirm the version is 6.2606.4246 or later.
- If you manage phones centrally through Intune or another mobile device manager, push the update rather than relying on individual employees to do it.
- Keep auto-updates turned on for Authenticator going forward — this kind of broker-app bug is exactly the sort of thing a routine update silently closes.
There’s no cleanup step required beyond updating the app — Microsoft says there’s no evidence this was exploited, so there’s no breach to investigate on your end. This is a “patch it and move on” situation, not a “check your logs” one.
The bigger pattern
This flaw had nothing to do with artificial intelligence — no AI model, no AI-written phishing email, nothing generated. It’s a plain software bug in how one app vouched for another app’s identity. It’s worth knowing about anyway, because it’s a reminder that the apps your business trusts to protect logins — authenticator apps, single sign-on brokers, password managers — are themselves pieces of software that can have bugs, and those bugs can undo the very protection you installed them for. Treat them the same way you’d treat any other critical business software: keep them updated, and don’t assume “security app” means “immune to security flaws.”
Full technical details on the flaw, from Microsoft’s CVE record and Enclave’s research, are covered in The Hacker News’ report. For more on keeping the everyday business tools you depend on secure, see AIWAS’s knowledge base, and follow @AIWASai on X for the next alert.
Stop leaving customers on read.
We answer your reviews, keep your social pages posting, and make your ads convert, so you get more customers while you run the business.
Get Started