The notable part of CVE-2026-80097 is not that an Android app walked off with a token for someone’s work account, it is how little the app needed in order to manage it. No permissions declared. No root. No exploit chain worth the name. It opened a screen inside Microsoft Authenticator, stated that it was Microsoft Teams, and the broker accepted the claim.
Security firm Enclave published the research on October 23, 2026, crediting researcher Ofek Levin through its fellowship program. Microsoft had already assigned the CVE on September 8 and shipped the fix in Microsoft Authenticator for Android version 6.2606.4246 as part of its September 2026 Patch Tuesday. Microsoft scored the flaw 8.6 on CVSS, labels it as important, and says it has not been used in attacks.
So this is not an emergency. It was found by researchers, reported quietly, and patched before anyone wrote about it. The useful question it raises is a duller one: who in your organization checks the version number of Authenticator on an employee’s personal Android phone? For most businesses the honest answer is nobody, and that gap is the actual story.
What Happened
On Android, Microsoft Authenticator is not just the thing that shows a six-digit code. It also works as a broker. When Teams or Outlook needs to sign a user in, it asks Authenticator, and Authenticator returns a token: a credential proving the user is already authenticated. That role makes the app a gatekeeper for the whole Microsoft estate on that device.
Enclave found that Authenticator exposed an activity named AccountChooserActivity that was marked as exported, meaning any installed app could start it. The only gate was a check that something had called it at all.
From there, the details of the token request came from whoever was asking. The claimed package name, the client ID, the redirect URI, the scopes and the caller’s UID were all supplied in the intent, and the researchers wrote all of them.
There was a signature check, and this is the part worth understanding. The check took the package name the caller claimed to be, looked up that package’s real signature on the device, derived the redirect URI that package would legitimately use, and compared it to the redirect URI in the request. Sound logic, wrong subject. Since genuine Teams was installed, its real signature was sitting right there for the attacking app to read and reproduce. The check verified the identity being impersonated instead of the one doing the impersonating, so it passed every time.
Enclave also notes that Authenticator could see the real calling package. It read that value and used it for internal bookkeeping, not for deciding whether to issue a token.
What came back was not modest. Posing as Teams and requesting Microsoft Graph returned scopes including Mail.ReadWrite, Mail.Send, Files.ReadWrite.All, Calendars.ReadWrite, ChatMessage.Send and Sites.ReadWrite.All. Access, refresh and ID tokens were returned to the calling app in plaintext. Impersonating Authenticator’s own client produced a different and arguably more unsettling set: UserAuthenticationMethod.ReadWrite, Passkey.Create and Passkey.Delete.
One point in the public record does not line up, and it is worth stating plainly rather than picking a side. Enclave reports that its proof of concept needed no user interaction beyond a work account being signed into the broker. Microsoft’s advisory, as The Hacker News summarized, says exploitation requires both a malicious app on the device and the user completing an authentication flow, and the CVSS vector reflects that user interaction requirement. Microsoft rates exploitation less likely, and the vulnerability was not in CISA’s Known Exploited Vulnerabilities catalog as of October 26, 2026.
Why This Matters for Businesses
Most organizations think of the authenticator app as a verification step. On Android it is closer to a key cabinet. The thing that approves your sign-ins is also the thing that hands out tokens for mail, files and SharePoint, which makes its version number a more interesting number than most people realize.
A stolen token also sits on the wrong side of the MFA prompt. It represents an authentication that already succeeded. An attacker holding one does not need to phish a code or fatigue anyone with push notifications, because the hard part is behind them.
The business exposure here is the familiar one. Delegated mailbox access is how invoice fraud and internal phishing start. Write access to files and SharePoint is a data protection problem and, for anyone carrying CMMC, HIPAA or similar obligations, a reportable one. None of that requires a dramatic intrusion story to be expensive.
Then there is the distribution problem, which is the real lesson. Patching programs tend to cover servers, laptops, firewalls and sometimes the phone operating system. Individual mobile app versions rarely appear anywhere. A corporate laptop gets the update whether its user cares or not. A personal Android phone with auto-update switched off, or with no Play Services connection for weeks, can sit on a vulnerable build of a security app for a very long time while everyone involved assumes MFA is handled.
One honest caveat: Microsoft’s advisory explains the fix but does not address whether updating invalidates a token that a malicious app already holds. That answer is not in the available sources, so nobody should assume the update retroactively closes the door.
What Organizations Should Consider
This is not a reason to move away from Authenticator. It is a reason to find out what you actually know about it. A few questions that travel well to an IT team or an MSP:
- Can we report, today, which Authenticator versions are running on the phones our staff use for work, and how many are below 6.2606.4246?
- Do we enforce a minimum app version through device management, or do we trust that people update their own phones?
- How many of those phones are personal devices we have no management relationship with at all, and what is our plan for that population?
- If a work account token were taken from a device, how would we notice? Would an unusual sign-in or a mailbox rule created by a token-bearing client show up in our review of Microsoft 365 sign-in and audit logs?
- Can we revoke sessions and refresh tokens for a single user quickly, and has anyone actually practiced doing it?
- Which applications in our tenant hold broad delegated permissions like Mail.Send or Files.ReadWrite.All, and when did we last read that list?
The encouraging part is that the first item on that list is usually a policy setting rather than a project. Requiring a minimum application version in Intune, or whatever device management you already pay for, takes a few minutes and covers every managed device from then on. The genuinely hard work is the unmanaged phones, and that is a conversation about enrollment and conditional access, not about buying another tool.
How ISM Can Help
This flaw lands squarely in identity, which is where we spend most of our time. Our Identity & Access Management work covers conditional access, device compliance and token lifetime policy: the controls that decide whether a token obtained on a phone is useful to anyone who shouldn’t have it. Cloud Solutions & Microsoft 365 covers the tenant side, including which applications hold which delegated permissions and whether your sign-in logs would surface something out of place.
Managed IT Services is where version enforcement actually lives. Keeping a minimum Authenticator version applied across managed Android devices, and knowing which devices are not managed at all, is ordinary patch hygiene extended to a category most patch programs never included. Our Cybersecurity & Risk Management practice helps decide how much the remaining BYOD gap is worth closing, which is a business judgment more than a technical one.
Talk With Our Team
If you do not currently have a way to answer “what version of Authenticator is on that phone,” that is a short and useful conversation to have, and we are happy to have it. Get in touch and we can look at how your mobile authentication is enrolled, managed and monitored, and what enforcing a minimum version would actually involve in your environment.
If you would rather take your own measurements first, the Cyber Maturity Calculator gives you a sense of where your identity and patching controls sit before you talk to anybody.