CVE-2026-80097
🟠 MediumMicrosoft Authenticator for Android (no iOS record exists). Not to be confused with CVE-2026-26123, the March 2026 deep-link OTP interception issue on Android and iOS, which is what most search results surface · >= 6.0.0 and < 6.2606.4246
CVSS (Koffei note)
8.6CVSS (v3.1, CVE List)
8.6EPSS (2026-11-18)
0.534%45.76th percentile
Exploitation
No exploitation found ; not in KEV ; SSVC 09/09/2026 reads exploitation none, automatable no, technical impact total. Microsoft's own vector encodes E:U, exploit code unproven. But the UI:R is now disputed rather than merely unexplained: the researchers who found it (Enclave, Ofek Levin, 23/10/2026) report their proof of concept returned tokens with no user interaction at all, while Microsoft maintains a user must complete an authentication flow. The two accounts are unreconciled, and if the researchers are right then AV:L with UI:R understates this
Timeline
- 08/09/2026CVE record published (CVE List)
- 27/10/2026Microsoft Authenticator flaw let permission-less Android apps steal work-account tokens
- 28/10/2026Microsoft Authenticator for Android let rogue apps steal sign-in tokens
- 29/10/2026CVE-2026-80097 — Microsoft Authenticator (Android) token theft
Risk
8.6 High (v3.1, Microsoft CNA) — AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C, EPSS 0.534% (CWE-287 : the exported
AccountChooserActivity could be started by any installed app, and the signature check compared the caller against the signature of the app being impersonated rather than the real caller — so merely having Teams installed made the check pass, and a permissionless app could obtain work-account tokens. The 8.6 comes from S:C, the scope change reaching the MFA identity itself)Fix
Yes — 6.2606.4246 through the Play Store ; no restart and no KB involved
Official description
Improper authentication in Microsoft Authenticator allows an unauthorized attacker to elevate privileges locally.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
CWE-287