The Authenticator fix is the September build
Microsoft's Authenticator advisory is CVE-2026-80097, fixed in Android build 6.2606.4246. Microsoft says it is not exploited. A later lab note disagrees about the prompt.
The short version
Microsoft's advisory says exploitation is not known. The fixed Android build is 6.2606.4246. A lab writeup disagrees about whether a prompt was required.
The advisory
Microsoft's update guide lists CVE-2026-80097 against Microsoft Authenticator for Android. The advisory was released on September 8, 2026, and last updated on September 15. The fixed build is 6.2606.4246. Microsoft rates it Important, with a CVSS score of 8.6. The exploited field says no, and the exploitation assessment says exploitation is less likely. Microsoft's description says a malicious app and a user completing an authentication flow. That is the vendor sentence. This page will not expand it into steps. The document named in the sources is the record this page will keep.
The later writeup
Enclave published a writeup on October 23. The lab says its test needed no user interaction beyond a signed-in work account. The Hacker News carried the story on October 27, which is why it is on today's wire. The disagreement is the news: Microsoft says a person completes a flow, and the lab says its test did not need an extra tap. This page will not describe the lab's method, the screen it used, or any permission list. The patch-window brief is the rule for a version line. The version line here is the September build.A patch window.
Who should update
The people in scope are Android users of Microsoft Authenticator on a build before 6.2606.4246 who use the app with a work account. Microsoft says the issue is not known to have been exploited. Updating the app to the fixed build is the action the advisory supports. A reader on a current build is outside the version line the advisory names. The CVE explainer on this desk is the general meaning of an identifier. This identifier is the September Authenticator entry.What a CVE identifier is.
What the October stories are
October 27 is the date outlets wrote about a researcher note. It is not the date Microsoft shipped the fix. Treating the wire date as the patch date would put the remedy a month late. The advisory page is the record for the build number, the score, and the exploited flag. The lab post is the record of a disagreement about interaction. The news posts are accounts of both. Asked directly, Who does the advisory put in scope? People using Microsoft Authenticator on Android with a work account, on a build before 6.2606.4246.The advisory is the story.
What this page leaves out
A writeup that demonstrates a token handoff is an attack note. This brief names the product, the identifier, the fixed build, and the disagreement about a prompt. It does not name components, extras, scopes, or a sequence. The iPhone Duo brief is a retail story about a different phone. It is linked so a mobile product on another desk is not mistaken for this Android app update. Asked directly, What severity did Microsoft assign? Important, with a CVSS score of 8.6. The exploited field on the advisory says no.The iPhone Duo.
Work accounts
Microsoft's scope is a work account in Authenticator on Android. A personal install that never signs in to a work tenant is not the case the advisory describes. The key-holder brief says a secret stays with the person who holds it. Here the vendor says the fixed build is the boundary, and the lab says the prompt was not the boundary it expected. Both sentences can be true as claims. Only Microsoft's page sets the build number. Asked directly, Why is an October story about a September advisory? The Hacker News wrote it up on October 27. The fix date on Microsoft's page remains September.The key stays with the holder.
The state of the flag
As of the advisory read for this filing, exploited is no. A later update from Microsoft could change that flag. An outlet headline that says tokens were stolen is describing the lab's result, not a breach list from Microsoft. This page will not convert a lab result into a victim count. No victim count appears in the advisory. Asked directly, What is the Authenticator identifier? CVE-2026-80097. Microsoft released the advisory on September 8, 2026, and updated it on September 15. The document named in the sources is the record this page will keep.
Filed once, on security
Authenticator is a phone app, and it would be easy to file it on the mobile desk beside Apple's version list. The dependency is the advisory, so it is filed here, once. Apple's October 26 list is a separate brief on the mobile desk. DreamHost is the other security filing today, and it has no CVE at all. The three documents should not be merged. Asked directly, Which Authenticator build does Microsoft say is fixed? Authenticator for Android 6.2606.4246. Builds before that are the ones the advisory names.DreamHost's status page.
The record
The record is Microsoft's advisory for the build, the score, and the exploited flag. Enclave is the source of the interaction disagreement, cited here without its procedure. The Hacker News is the October 27 account. The fixed build remains 6.2606.4246. The advisory date remains September 8, 2026. The short answer this page will stand on is this: Microsoft's advisory says exploitation is not known. The fixed Android build is 6.2606.4246. A lab writeup disagrees about whether a prompt was required. The document named in the sources is the record this page will keep.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
What is the Authenticator identifier?
CVE-2026-80097. Microsoft released the advisory on September 8, 2026, and updated it on September 15.
Which Authenticator build does Microsoft say is fixed?
Authenticator for Android 6.2606.4246. Builds before that are the ones the advisory names.
What severity did Microsoft assign?
Important, with a CVSS score of 8.6. The exploited field on the advisory says no.
Who does the advisory put in scope?
People using Microsoft Authenticator on Android with a work account, on a build before 6.2606.4246.
Why is an October story about a September advisory?
The Hacker News wrote it up on October 27. The fix date on Microsoft's page remains September.