We use optional cookies to improve your experience on our websites, such as through social media connections, and to display personalized advertising based on your online activity. If you reject optional cookies, only cookies necessary to provide you the services will be used. You may change your selection by clicking “Manage Cookies” at the bottom of the page. Privacy Statement Third-Party Cookies Accept Reject Manage cookies MSRC Customer Guidance Security Update Guide Vulnerabilities CVE-2026-41615 Microsoft Authenticator Information Disclosure Vulnerability New On this page CVE-2026-41615 Subscribe RSS PowerShell API CSAF Security Vulnerability Released: May 14, 2026 Assigning CNA Microsoft CVE.org link CVE-2026-41615 Impact Information Disclosure Max Severity Critical Weakness CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CVSS Source Microsoft Vector String CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C Metrics CVSS:3.1 9.6 / 8.3 Base score metrics: 9.6 / Temporal score metrics: 8.3 Expand all Collapse all Metric Value Base score metrics(8) Attack Vector Network Attack Complexity Low Privileges Required None User Interaction Required Scope Changed Confidentiality High Integrity High Availability High Temporal score metrics(3) Exploit Code Maturity Unproven Remediation Level Official Fix Report Confidence Confirmed Please see Common Vulnerability Scoring System for more information on the definition of these metrics. Executive Summary Exposure of sensitive information to an unauthorized actor in Microsoft Authenticator allows an unauthorized attacker to disclose information over a network. Exploitability The following table provides an exploitability assessment for this vulnerability at the time of original publication. Publicly disclosed No Exploited No Exploitability assessment Exploitation Less Likely FAQ **What type of information could be disclosed by this vulnerability? ** This vulnerability could expose a sign-in access token for a user’s work account. If disclosed, that token could allow access to data and services that the user is authorized to use, potentially including sensitive organizational information. How could an attacker exploit this vulnerability? An attacker could attempt to trick a user into interacting with a malicious request that appears legitimate. When the user approves the request, the attacker could cause the app to obtain an access token on the user’s behalf and send it to a location controlled by the attacker, without the user being clearly informed about what access is being granted. Do users need to take any action to receive the fix for the Authenticator app issue on Android? Users who have automatic app updates enabled on their Android device will receive the fix without any action required. Users who do not have auto-update enabled must manually update the Microsoft Authenticator app to the latest version via the Google Play Store to ensure they receive the fix. According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability? An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. Acknowledgements Sridhar Periyasamy Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information. Security Updates To determine the support lifecycle for your software, see the Microsoft Support Lifecycle. Release date Descending Edit columns Download Filters Product Family Max Severity Impact Platform Clear Release date Product Platform Impact Max Severity Article Download Build Number Assigning CNA Customer Action Required Title: Release date, Content: May 14, 2026 Microsoft Authenticator for IOS - Information Disclosure Critical Title: Knowledge Base Articles for Microsoft Authenticator for IOS, Content:, 1 link Release Notes Title: Download Security Update for Microsoft Authenticator for IOS, Content:, 1 link Security Update Title: Build numbers, Content: 6.8.47 Title: Assigning CNA, Content: Microsoft Title: Customer action required, Content: Required Title: Release date, Content: May 14, 2026 Microsoft Authenticator for Android - Information Disclosure Critical Title: Knowledge Base Articles for Microsoft Authenticator for Android, Content:, 1 link Release Notes Title: Download Security Update for Microsoft Authenticator for Android, Content:, 1 link Security Update Title: Build numbers, Content: 6.2605.2973 Title: Assigning CNA, Content: Microsoft Title: Customer action required, Content: Required All results loaded Loaded all 2 rows Disclaimer The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. Revisions version revisionDate description 1.0 May 14, 2026 Information published. How satisfied are you with the MSRC Security Update Guide? Rating Broken Bad Below average Average Great! Your Privacy Choices Consumer Health Privacy
CVE-2026-41615 is a critical (CVSS 9.6) information disclosure vulnerability in Microsoft Authenticator where an attacker can trick a user into approving a malicious request, causing the app to obtain and exfiltrate the user's work account access token over a network. The article states exploitation is assessed as less likely but does not provide specific affected or fixed version numbers; it only notes that Android users must manually update via the Google Play Store if automatic updates are disabled.