Cybersecurity Updates & Tools

Microsoft Authenticator Flaw Could Leak Login Codes

A newly disclosed vulnerability in Microsoft Authenticator could expose one time sign in codes or authentication deep links to a malicious app installed on the same mobile device. The issue, tracked as CVE-2026-26123, affects both Android and iOS and was published on March 10, 2026. Public CVE data rates the flaw as Medium severity with a CVSS 3.1 score of 5.5, and classifies it as a local attack that requires user interaction. The weakness is tied to CWE-939, which covers improper authorization in handlers for custom URL schemes.

Microsoft Authenticator is widely used to generate time based one time passcodes and process sign in links or QR based logins for Microsoft and other accounts. Deep links are specially structured URIs that open an app directly and trigger a specific action, such as completing a login. Because the app is commonly used on personal phones, including BYOD devices connected to business services, the impact could extend beyond consumer accounts into corporate environments.

CVE Snapshot

ItemDetails
CVECVE-2026-26123
ProductMicrosoft Authenticator
PlatformsAndroid and iOS
SeverityMedium
CVSS5.5
Attack VectorLocal
User InteractionRequired
WeaknessCWE-939
Main RiskDisclosure of sign in data or one time codes

The available advisories show that exploitation is not automatic. A victim would first need to install a rogue app and then accidentally allow that app to handle a sign in deep link. If that happens, the malicious app may receive the one time code or sign in information and use it to complete authentication as the victim. From there, an attacker could reach email, files, cloud apps, or even production systems tied to the compromised account. Malwarebytes also warns that attackers may pivot to additional accounts protected by codes delivered through the same device.

What Users Should Do

The fix is already included in current releases. According to the CVE record, affected versions include Microsoft Authenticator for Android 6.0.0 through before 6.2511.7533 and Microsoft Authenticator for iOS 6.0.0 through before 6.8.40. Users should update the app immediately through Google Play or the App Store. If updating is not possible right away, avoid newly installed apps that ask to handle authentication links, verify that Microsoft Authenticator is the selected handler for login prompts, and use trusted anti malware protection on mobile devices.

Prevention StepWhy It Matters
Update Microsoft Authenticator immediatelyInstalls the vendor fix for CVE-2026-26123
Avoid unknown or newly installed appsReduces the chance of a rogue app intercepting sign in data
Check which app opens sign in linksHelps ensure Microsoft Authenticator handles the authentication flow
Be careful with QR based loginsPrevents accidental redirection to a malicious handler
Use mobile security protectionCan help flag suspicious apps on the device
Review installed apps regularlyHelps remove software that could abuse authentication links