Security readout for executives and security teams
Plain-English summary
Microsoft Authenticator 6.0.0 on Android and iOS has a local information disclosure issue. The CVSS rating is medium because exploitation requires local access and user interaction, but successful exploitation could expose highly sensitive information. Treat this as a mobile identity-app risk, not a remote network compromise.
Executive priority
Handle in the normal vulnerability cycle with elevated attention for privileged users and mobile MFA populations. The risk is meaningful because confidentiality impact is high, but current evidence does not justify emergency response without additional exploitation indicators.
Technical view
CVE-2026-26123 affects Microsoft Authenticator for Android and iOS version 6.0.0. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. Microsoft classifies it as information disclosure and references CWE-939. The bundle does not provide root-cause detail, exposed data type, or exact fixed version.
Likely exposure
Exposure is limited to endpoints running Microsoft Authenticator for Android or iOS version 6.0.0. Organizations with mobile MFA deployments, BYOD access, or unmanaged authenticator installations should assume some exposure until app versions are verified.
Exploitation context
The provided sources do not support active exploitation. KEV status is false, and CVSS exploit maturity is unproven. The attack is local, requires no privileges, and requires user interaction, which reduces broad automated exploitation risk.
Researcher notes
Public detail is sparse. Do not infer affected versions beyond 6.0.0 or data exposure specifics from the bundle. Useful follow-up is vendor advisory tracking, app version validation, and any future Microsoft clarification on root cause and fixed builds.
Mitigation direction
- Follow Microsoft MSRC guidance for CVE-2026-26123.
- Update Microsoft Authenticator through official app stores or MDM channels.
- Prioritize managed mobile devices used for privileged or remote access.
- Use MDM compliance policies to block outdated Authenticator versions.
- Monitor Microsoft advisory updates for fixed-version details.
Validation and detection
- Inventory Microsoft Authenticator versions on Android and iOS devices.
- Confirm whether version 6.0.0 is installed anywhere.
- Check MDM and app-store update compliance status.
- Record MSRC advisory status and remediation evidence.
- Verify KEV remains false before changing exploitation assumptions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-939: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-26123 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C1.83.6microsoftVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Authenticator Information Disclosure VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authorization in Handler for Custom URL Scheme
Improper Authorization in Handler for Custom URL Scheme represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.