iPhone flaw let apps record audio after microphone access was denied
Apple has fixed a bug in its audio system that let an installed app keep recording from the microphone after the user had refused it access. The flaw is tracked as CVE-2026-65339. Patches have been out since August 17, and the last of them, for older iPhones, arrived on October 26. Detailed technical write-ups and proof-of-concept code went public on November 9, so devices that still haven't updated are now running a bug that anyone can read about.
What happened
On iPhone, iPad and Mac, an app can't decide for itself whether it may use the microphone. The request goes to the system's privacy layer, TCC (Transparency, Consent, and Control), which checks the user's choice for that specific app.
Recording itself runs through a system audio service called audiomxd. To know which app it was serving, the service relied on an audit token, a small record that identifies a process. The problem was that it accepted a token supplied by the app instead of the one the operating system attaches to every request.
An app could therefore hand the service a token that named audiomxd itself. The service then treated the app as itself, took an internal shortcut meant for its own audio, and allowed recording without asking TCC. The user's "Don't Allow" was never consulted. The permission prompt appeared once, at first launch, and declining it did not stop the recording.
On an earlier iOS 27 beta build, the orange microphone indicator also stayed off during recording, and the system logs pointed to the audio service rather than the app. On a later build the indicator was showing again. So the orange dot was not a dependable warning while the flaw was present.
Who is affected
Apple lists the fix for these releases:
- iOS 26.6.1 and iPadOS 26.6.1 (August 17): iPhone 11 and later, plus supported iPad Pro, iPad Air, iPad and iPad mini models
- iOS 18.7.11 and iPadOS 18.7.11 (October 26): iPhone XS, iPhone XS Max, iPhone XR and iPad 7th generation
- macOS Tahoe 26.6.2 (August 17)
- macOS Sequoia 15.8, tvOS 27, watchOS 27 and visionOS 27 (September 14)
Anything older than those versions is affected. The full device list is in Apple's iOS 26.6.1 security notes. Apple's notes for iOS 27 do not mention the CVE, although the fix first shipped in an iOS 27 beta on August 10.
How serious it is
The bug cannot be triggered remotely. A malicious app has to be installed and running on the device. It needed no special entitlements, only the ordinary sandbox every App Store app runs in. The bypass covered the microphone through this audio path. It did not give the app access to the camera, location, contacts or other protected data.
Apple describes the issue only as a logic problem that "may" let an app leak sensitive user information. CISA scored it 5.0 out of 10 (medium) and reported no known exploitation; the NVD entry carries that score. The flaw is not in CISA's Known Exploited Vulnerabilities catalog, and no attacks using it have been reported.
That medium score understates how it feels in practice. A microphone that records after you said no, with no orange dot on some builds, is the kind of thing spyware is built around. With working code now public, the risk for unpatched devices goes up.
How Apple fixed it
The service now checks the real caller's identity, which the kernel supplies, before letting anyone replace the stored client identity. Only a caller holding a private Apple entitlement (com.apple.private.audio.client-audit-token-override) can do that, and an app cannot grant that entitlement to itself.
What to do now
- Update. No setting blocks the bypass, so the update is the fix. On iPhone and iPad go to Settings > General > Software Update. You need iOS 26.6.1 or later, or iOS 18.7.11 on the older models that can't run iOS 26. On a Mac, install macOS Tahoe 26.6.2 or Sequoia 15.8 or later.
- Check managed fleets. In your MDM, list devices still below the fixed versions and push the update. Older iPhones that only received the fix in late October are the ones most likely to lag.
- Review app permissions. In Settings > Privacy & Security > Microphone, remove access from apps that don't need it, and uninstall apps you don't recognise or no longer use. There is no reliable way to tell after the fact whether an app abused this flaw, so cutting down the number of installed apps is the practical defence.
The root mistake here, a service trusting an identity the caller hands it, is not unique to Apple. The same pattern turns up in web APIs and backend services that accept a user or tenant ID from the request instead of from the authenticated session. That is one of the authorisation checks our penetration testing team works through on client applications.
