The patched CVE-2026-65339 vulnerability in Apple’s audio subsystem allowed a sandboxed app on iPhone and iPad to record audio through the microphone even after the user had explicitly denied the access request. On early affected builds, recording was not accompanied by the orange status bar indicator and was not logged as app activity in the system logs. Apple released fixes starting August 17, 2026 for iOS, iPadOS, macOS, tvOS, watchOS, and visionOS. Neither Apple nor the researchers who discovered the vulnerability report its use in real-world attacks; however, the absence of such data does not rule out that exploitation could have occurred unnoticed. The only way to protect against it is to install updates.
Technical essence of the vulnerability
The root cause lies in the audiomxd daemon, Apple’s system audio service. This daemon is responsible for handling audio streams and, during normal operation, interacts with the Transparency, Consent, and Control (TCC) subsystem, which checks whether the calling process has permission to access the microphone. Each process in the system is identified by an audit token — a unique marker provided by the kernel.
According to the technical analysis by Nick Tsytsarkin of Meta Red Team X, the audiomxd daemon accepted the audit token supplied by the app itself instead of using the token provided by the kernel. The app could send a token that identified it as audiomxd. The daemon treated such a request as its own internal call and allowed recording while bypassing the TCC check. The kernel itself supplied the app with the data needed to spoof the service’s identity.
According to an independent study by Mustafa Kalap, who reproduced the vulnerability separately, the test apps were standard sandboxed applications without additional entitlements. The only privacy key was NSMicrophoneUsageDescription, required to display the system microphone access prompt. Kalap reproduced the bypass on iOS 26.6 and a beta version of iPadOS 27.
Behavior during exploitation
According to the researchers, on first launch the system displayed the standard microphone access prompt. If the user tapped “Don’t Allow,” recording nevertheless continued. On subsequent launches of the app, the prompt no longer appeared. On an early test build, the orange microphone indicator in the Dynamic Island did not light up, and in the system logs the recording was attributed to the audiomxd daemon, not the app. This means that the absence of an orange indicator or of log entries about microphone use by an app cannot serve as reliable retrospective evidence that no recording took place.
Kalap determined that recording had to be started while the app was in the foreground. However, once started, it continued when the app moved to the background and even after the device was locked (with the UIBackgroundModes = audio flag set). The bypass affected only microphone capture through the audio service and did not grant the app any other TCC permissions.
Both test apps were installed via Xcode and did not go through App Review. The research does not establish whether App Review would have blocked such an app if it had been submitted to the App Store.
Fixes and affected platforms
Apple released fixes for CVE-2026-65339 in the following updates:
- iOS 26.6.1 and iPadOS 26.6.1 (August 17, 2026) — for iPhone 11 and later, iPad Pro 12.9" 3rd generation and later, iPad Pro 11" 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, iPad mini 5th generation and later
- iOS 18.7.11 and iPadOS 18.7.11 (October 26, 2026) — for iPhone XS, iPhone XS Max, iPhone XR, and iPad 7th generation
- macOS Tahoe 26.6.2 (August 17, 2026)
- macOS Sequoia 15.8 (September 14, 2026)
- tvOS 27, watchOS 27, and visionOS 27 (September 14, 2026)
The researchers did not test the vulnerability on macOS, tvOS, watchOS, or visionOS, even though Apple shipped fixes for these platforms as well. The fix is that audiomxd now verifies the real identity of the calling process using the token provided by the kernel. Overriding the client token now requires the private entitlement com.apple.private.audio.client-audit-token-override, which a regular app cannot assign to itself.
Discrepancies in the documentation
It is worth noting several discrepancies. In its advisories, Apple described the vulnerability only as a possible “leak of users’ confidential information,” without mentioning either the microphone permission bypass or the absence of the orange indicator. In addition, the iOS 27 release notes contain no mention of CVE-2026-65339 at all, although according to Meta Red Team X, the fix was included in iOS 27.0 beta 5 from August 10, 2026. Earlier, we already wrote about Apple backporting patches to older devices in the context of the iOS 18.7.11 update, which also contains a fix for this vulnerability.
Recommendations
The researchers do not describe any setting or workaround that would block the vulnerability without updating. There is also no way to retrospectively verify whether data was recorded before the patch was installed. Recommended actions:
- Install the relevant update from the list above for every Apple device in your infrastructure
- Pay special attention to iPhone XS/XR devices and iPad 7th generation: the patch for them was released only on October 26, two months after the main fix
- Check the OS version on corporate devices via your MDM system
Installing updates is the only confirmed protection against CVE-2026-65339. Owners of Apple devices, especially older iPhone XS/XR models, should make sure iOS 18.7.11 or a later version is installed, since before this update an app on the device could potentially record from the microphone without the user’s knowledge and without visible indicators.












