The short version
- The flaw. CVE-2026-65339 sat in audiomxd, the service that handles audio on Apple devices. It accepted an app's claim about which process was asking for audio and then took an internal shortcut that skipped the permission check, so recording continued after the user tapped Don't Allow.
- The fix. Apple's first updates carrying the fix shipped on 17 August, starting with iOS 26.6.1 and iPadOS 26.6.1. The service now checks the real caller's identity, which the kernel supplies.
- Researcher findings. Nik Tsytsarkin of Meta Red Team X and security engineer Mustafa Calap each built test apps that recorded with microphone permission denied. In Calap's tests, recording had to begin while the app was in the foreground, then continued in the background and with the device locked.
- No sign of abuse. Neither Apple nor the researchers report the flaw being exploited. CISA scores it 5.0 out of 10 and has not added it to its catalogue of known exploited vulnerabilities.
Timeline
| Date | Event |
|---|---|
| 27 July | iOS 26.6 is released; Calap later reproduces the bypass on it. |
| 10 Aug | Meta's timeline records the fix shipping in iOS 27.0 beta 5. |
| 17 Aug | Apple releases iOS 26.6.1, iPadOS 26.6.1 and macOS Tahoe 26.6.2 with the fix. |
| 14 Sept | Updates for macOS Sequoia, tvOS, watchOS and visionOS follow. |
| 26 Oct | iOS 18.7.11 and iPadOS 18.7.11 cover older iPhone and iPad models. |
| 17 Nov | A report sets out the flaw and the fix, with both researchers' write-ups public. |
How the bypass worked
Whether an app may record is normally decided by Transparency, Consent, and Control (TCC), the system that checks which process is making the request. The audio service, audiomxd, did not verify that for itself. An audit token identifies a process, and an app could send the service a token naming audiomxd. The service then treated the app as itself and allowed recording through an internal route that never consulted TCC. The kernel handed the app the details it needed to pose as the service.
The patch makes the service confirm the caller's real identity from kernel-supplied data. Outside callers now need a private entitlement that an app cannot grant itself. The two test apps were sandboxed with no added entitlements; their only privacy key was NSMicrophoneUsageDescription, the setting that makes the microphone prompt appear.
What the tests showed, and what they did not
In Tsytsarkin's tests the prompt appeared the first time the app opened. Declining it did not stop the recording and the prompt did not return on later launches. Calap reproduced the bypass on iOS 26.6 and on an iPadOS 27 beta. The bypass only covered microphone capture through the audio service; it gave the app no other privacy permissions.
Both apps were loaded from Xcode and never passed App Review, so the tests do not show whether review would have stopped such an app. The orange indicator behaved inconsistently across builds: it stayed off on one earlier build, and Tsytsarkin says his video was made on a later build that appears to have restored it. Neither researcher describes a way for a user to check afterwards whether an app had recorded them. Neither researcher reports testing macOS, tvOS, watchOS or visionOS, though fixes are listed for those systems.
The fix and how it was described
The first patched releases were iOS 26.6.1 and iPadOS 26.6.1 on 17 August, alongside macOS Tahoe 26.6.2. Further updates covered macOS Sequoia, tvOS, watchOS and visionOS on 14 September, and older iPhones and iPads on 26 October. Apple's notes for the iOS 27 releases do not list the flaw, although Meta's timeline says the fix shipped in iOS 27.0 beta 5 on 10 August.
Apple's August notes describe the issue only as one that may let an app leak sensitive user information. Tsytsarkin wrote: "That description leaves out the most striking part: the app could record after permission was denied, without the orange indicator appearing." CISA gives the flaw a CVSS score of 5.0 out of 10 and had not listed it in its known exploited vulnerabilities catalogue as of its latest update. The researchers describe no setting that blocks the bypass, leaving the updates as the remedy.
What is not known yet
- Whether any app outside the researchers' test builds used the bypass.
- How long the flaw existed before the 17 August fix.
- How many devices were running affected versions during that period.
- Whether App Review would have detected a malicious app relying on it.
- Why the iOS 27 release notes omit the flaw when an earlier beta is said to have fixed it.
What to do
If you manage iPhones and iPads
- Update supported devices to iOS 26.6.1 and iPadOS 26.6.1 (17 August) or later.
- Check Apple's advisory for the update covering older models such as iPhone XS, XR and iPad 7th generation, released on 26 October.
- Enforce a minimum OS version through mobile device management so devices cannot stay on builds older than the fixes.
If you manage other Apple devices
- Apply the macOS, tvOS, watchOS and visionOS updates that Apple lists for this flaw, even though the researchers did not test those platforms.
For everyone else
- Treat the orange microphone indicator as a signal rather than a guarantee on unpatched devices: the researchers found builds where recording continued without it.
- Patch Apple devices promptly, since there is no setting that blocks this bypass and no way to check after the fact whether an app recorded.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.