Improper authentication in Microsoft Authenticator for Android from Microsoft enables local privilege escalation

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-80097?

CVE-2026-80097 is a vulnerability classified as Improper Authentication, affecting Microsoft Authenticator for Android (affected versions: 6.0.0 – < 6.2606.4246). This vulnerability is rated High, with a CVSS score of 8.6. Current sources do not report this vulnerability as exploited.

Overview

Original source data

Improper authentication in Microsoft Authenticator allows an unauthorized attacker to elevate privileges locally.

Affected products and scope

  • Microsoft Authenticator for Android: versions 6.0.0 through versions less than 6.2606.4246 are identified as affected.
  • Fixed build: Microsoft identifies 6.2606.4246 as fixed. The current VEX also records that the fix build number was corrected in a later revision.
  • The supplied record does not establish the status of parallel Android branches or versions outside the stated boundary.

Technical details

Microsoft Authenticator for Android contains an Improper Authentication weakness classified as CWE-287. The record confirms that the flaw is in the application's authentication handling, but it does not identify the specific authentication check, protected resource, or attacker-controlled input that is mishandled.

The supplied attack conditions describe local reachability, no required prior privileges, low complexity, and required user interaction. The scope is marked as changed, indicating that a successful attack may cross the original security boundary of the affected component. Public detail is not sufficient to describe an exploit sequence or more specific application preconditions without speculation.

Exploitability

  • Reachability: Local on an Android device, not network reachable.
  • Conditions: No prior privileges are required, complexity is low, and user interaction is required.
  • Known status: The supplied record does not identify a public exploit and does not mark the vulnerability as known exploited. Microsoft's VEX describes exploit code maturity as unproven.
  • No specific campaign, victim, payload, or indicator of compromise is identified in the public evidence reviewed.

Technical impact

The flaw may allow a local attacker with no prior privileges to bypass or subvert authentication handling and obtain higher privileges. Exploitation requires user interaction, but the stated complexity is low and no prior authentication is required. With changed scope, the result may affect resources beyond the original security boundary of the vulnerable component. The recorded impact includes high potential consequences for confidentiality, integrity, and availability, while the record does not specify the exact privilege gained, affected resources, or whether a real-world attack has occurred.

Business impact

  • An affected device may allow an unprivileged local user or process to obtain higher privileges through the authentication flaw.
  • If exploitation succeeds, the attacker may affect data, operations, or service state within the authority granted by the elevated privileges.
  • The scope is marked as changed, so consequences may extend beyond the original security boundary of the vulnerable component.
  • The record does not identify the target privilege, specific assets, or a confirmed incident scenario. A data breach or service outage should not be inferred without separate evidence.

Remediation

  1. Update Microsoft Authenticator for Android to 6.2606.4246, the fixed build identified by Microsoft.
  2. Deploy the update through the application's official distribution channel and verify the installed version afterward.
  3. Prioritize devices within the affected range, especially devices that do not receive automatic updates or are not centrally managed.
  4. If updating is not immediately possible, the supplied record does not provide a separate vendor mitigation. Continue tracking Microsoft guidance and do not treat generic monitoring as a substitute for the application update.

Detection

  1. Inventory Android devices that have Microsoft Authenticator installed and record the installed application version.
  2. Compare installed versions with the affected boundary and fixed build stated in affected_summary.
  3. Prioritize devices that have not received the official application update or are outside centralized application management.
  4. Review application-management telemetry for update status and relevant user interaction involving the application. Treat this as precautionary monitoring, not as a vendor-confirmed indicator.
  5. No specific log event, endpoint, IOC, or authentication trace is provided. The absence of matching log evidence does not prove that a device is safe.
Sources (11)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.