Patch available CVSS 5.0 Security news

iPhone flaw let apps record audio even after you denied microphone access

On 9 November 2026 Meta Red Team X published a write-up of CVE-2026-65339, a bug in Apple's audio service. It let an installed app record from the microphone even after the user tapped “Don't Allow”, and according to the researcher the orange indicator never appeared. Apple fixed it back in August, so an up-to-date device is all you need. No exploitation has been reported.

Kyberkit editorial team · · event date · reading time 4 minutes · For everyone

Patch available: Apple audiomxd, CVE-2026-65339, CVSS 5.0

Key points

  • CVE-2026-65339 in Apple's audiomxd service let an installed app record from the microphone without permission, even after the user had denied access.
  • According to the Meta Red Team X researcher, the orange indicator did not appear on vulnerable builds and the recording was logged against the system service rather than the app.
  • Apple fixed the bug on 17 August 2026 in iOS and iPadOS 26.6.1 and macOS Tahoe 26.6.2, and later in older and other platforms (most recently iOS 18.7.11 on 26 October).
  • No exploitation has been reported. Devices updated since August are protected, but the detailed write-up makes unpatched devices a more attractive target.

Vulnerabilities: CVE-2026-65339

What happened

On 9 November 2026, Nik Tsytsarkin of Meta Red Team X published a detailed write-up of CVE-2026-65339, a bug in Apple's audio service. Security engineer Mustafa Calap reported the same flaw independently, and Apple credits both.

The bug let an app installed on an iPhone or iPad record from the microphone without permission. Tapping “Don't Allow” on the microphone prompt made no difference.

Apple fixed it on 17 August 2026 (iOS and iPadOS 26.6.1). For most people, the only task is to confirm their device is up to date.

Technical details

  • Component: the audiomxd system service, which brokers audio on iOS. Apple's bulletin lists it as “Audio”.
  • Bug class: Apple describes a logic issue addressed with improved checks; NVD classifies it as a protection mechanism failure (CWE-693). The secondary CVSS 3.1 score in NVD is 5.0 (medium).
  • How the attack worked (defensive view): according to Meta Red Team X, when deciding on microphone access the service trusted an identity value that the app itself supplied. An app could therefore pass itself off as the audio service, which then skipped the privacy (TCC) check.
  • Preconditions: a malicious app had to be installed on the device. According to the researcher, it needed no special entitlements.
  • Why it mattered: on the vulnerable build, the researcher says, the orange microphone indicator did not appear, and the recording was attributed to audiomxd in system logs rather than to the app.

Who is affected

Systems older than these fixed releases are vulnerable:

  • iOS and iPadOS 26.6.1 (17 Aug 2026) – iPhone 11 and later, recent iPads
  • macOS Tahoe 26.6.2 (17 Aug 2026) and macOS Sequoia 15.8 (14 Sep 2026)
  • tvOS 27, watchOS 27 and visionOS 27 (14 Sep 2026)
  • iOS and iPadOS 18.7.11 (26 Oct 2026) – iPhone XS, XS Max, XR and iPad (7th generation)

Anyone on iOS 27 or any later release in this list is protected.

How to tell if you were compromised

Neither Apple nor the researchers have published indicators of compromise or reported exploitation. Because the bug hid both the orange indicator and the true source of the recording, a typical user would not have noticed an attack. What you can do (our recommendations):

  • Check Settings → Privacy & Security → Microphone to see which apps have asked for access.
  • Uninstall apps you don't recognise, don't use, or that come from an unknown developer.
  • Device administrators can use their MDM inventory to find devices below the fixed versions.

What to do

  1. iPhone and iPad: Settings → General → Software Update – install the latest version, at least iOS 26.6.1 (18.7.11 on iPhone XS and XR).
  2. Mac: System Settings → General → Software Update – at least macOS 26.6.2 or 15.8.
  3. Turn on automatic updates so fixes arrive on their own.
  4. Organisations: enforce the minimum versions above in MDM; the public write-up raises the risk for devices that have fallen behind.

Timeline

Timeline of CVE-2026-65339 from report to public write-up7 Jul 2026: Meta Red Team X reports the bug to Apple; 10 Aug 2026: Fix lands in iOS 27 beta 5; 17 Aug 2026: iOS and iPadOS 26.6.1, macOS 26.6.2; CVE published in NVD; 14 Sep 2026: macOS 15.8, tvOS, watchOS and visionOS 27; 26 Oct 2026: iOS 18.7.11 for older iPhones; 9 Nov 2026: Detailed write-up published7 Jul 2026Meta Red Team X reports thebug to Apple10 Aug 2026Fix lands in iOS 27 beta 517 Aug 2026iOS and iPadOS 26.6.1, macOS26.6.2; CVE published in NVD14 Sep 2026macOS 15.8, tvOS, watchOS andvisionOS 2726 Oct 2026iOS 18.7.11 for older iPhones9 Nov 2026Detailed write-up published
Based on Meta Red Team X, Apple and NVD

Updates

  • 17 November 2026 – first version of this article.

FAQ

Could an app have been listening to me?

In theory, yes, if you had a malicious app installed and an unpatched system. Neither Apple nor the researchers know of any exploitation. iOS 26.6.1 and later fix the bug.

Did an attacker need physical access to my phone?

No. The attack needed an installed app, and according to the researcher it required no special entitlements. Whether such an app would have passed App Store review was not tested.

I have an iPhone XS or XR. What should I do?

Apple shipped the fix for those models on 26 October 2026 in iOS 18.7.11. Check that it is installed.

Is there anything else to do after updating?

We recommend reviewing Settings → Privacy & Security → Microphone and deleting any apps you don't recognise or no longer use.

Sources

  1. Meta Red Team X – CVE-2026-65339 write-up (9 Nov 2026)
  2. Apple – About the security content of iOS 26.6.1 and iPadOS 26.6.1
  3. Apple – About the security content of iOS 18.7.11 and iPadOS 18.7.11
  4. Apple – About the security content of macOS Tahoe 26.6.2
  5. NVD – CVE-2026-65339

Spotted a mistake? Let us know and we will correct it openly.