← Voltar ao feed
medium

Apple audiomxd flaw CVE-2026-65339 lets sandboxed apps record microphone audio without TCC permission; patched across Apple platforms

2 fonte(s) · 2 atualização(ões) · publicado 16/11/2026 08:42 · coletado há 5 horas

A flaw in Apple's audio media daemon (audiomxd), tracked as CVE-2026-65339, let a sandboxed app record microphone audio without user permission, even after the user denied the prompt. On an earlier build it also hid the orange privacy indicator. Meta Red Team X researcher Nik Tsytsarkin disclosed it, and Mustafa Calap reported the same flaw separately. Apple's advisory describes it only as an Audio issue where an app may leak sensitive user information. Apple fixed it first in iOS 26.6.1, iPadOS 26.6.1 and macOS Tahoe 26.6.2 (Aug 17), then in macOS Sequoia 15.8, tvOS 27, watchOS 27 and visionOS 27 (Sep 14) and iOS/iPadOS 18.7.11 (Oct 26) (thehackernews.com). Neither Apple nor the researchers report exploitation in the wild, and CISA's KEV catalog does not list it. CISA gives it CVSS 5.0 (thehackernews.com). It is a local flaw: the attacker needs an app already installed on the device, and recording had to start in the foreground. The bypass covers only microphone capture through this audio path and does not grant general TCC permissions.

Entenda a falha

A vulnerabilidade

CVE-2026-65339 is a flaw in audiomxd, Apple's audio media daemon, that let a sandboxed app record microphone audio without TCC permission, even after the user tapped Don't Allow. On an earlier build the orange privacy indicator also stayed off. It is local: the app must already be installed, and recording had to start in the foreground. It covers only microphone capture through this audio path, not other permissions. CISA rates it CVSS 5.0. Fixed in iOS/iPadOS 26.6.1 and macOS Tahoe 26.6.2 (Aug 17), macOS Sequoia 15.8, tvOS 27, watchOS 27 and visionOS 27 (Sep 14), and iOS/iPadOS 18.7.11 (Oct 26). No exploitation in the wild is reported and it is not in CISA's KEV.

Como funciona

audiomxd runs the server side of AURemoteIO, the audio unit used for low-latency recording. Normally TCC decides whether a process may use the microphone, based on which process is asking. The app sends a request to set property 2009, and the handler copies the app-supplied 32-byte audit token into its client object. AQIONodeClient::SetCanRecord() then compares that token's PID and process version with audiomxd's own. If they match, it treats the audio as internal to the daemon and allows recording without asking TCC. The logs then name the daemon as the recorder, so no app appears to be using the microphone.

Por que é vulnerável

The daemon trusted an identity value supplied by the application. The property 2009 handler never checked it against the caller's real audit token, which the kernel provides, and it required no entitlement or code-signing check. Since a matching PID and process version counted as proof that the caller was audiomxd, a forged token was enough to skip TCC. The fix makes the service check the real caller identity from the kernel. Outside callers now need the private entitlement com.apple.private.audio.client-audit-token-override, which an app cannot grant itself.

Onde está

According to the researchers' analysis, the flaw is in audiomxd: the property 2009 handler in AUIOServer_SetProperty and the check in AQIONodeClient::SetCanRecord().

Como foi descoberta

Nik Tsytsarkin of Meta Red Team X found and disclosed the flaw, and security engineer Mustafa Calap reported the same flaw separately. The articles do not say how it was found or when it was reported. Meta's timeline says the fix shipped in iOS 27.0 beta 5 on 10 August 2026, and Apple's first public updates came on 17 August. Tsytsarkin published the technical details and Calap published his own analysis the same day, about a week before the November 17 article. Apple's advisory describes it only as an Audio issue where an app may leak sensitive user information, which Tsytsarkin says leaves out the most striking part.

PoC existente, privada

O exploit existe, mas quem o tem não o publicou.

Both researchers demonstrated the bypass. Meta's demo video shows a test app recording without microphone permission, filmed on a later build that appears to have restored the indicator. Calap reproduced it on iOS 26.6 and an iPadOS 27 beta with sandboxed test apps installed from Xcode, with recording continuing in the background and with the device locked. The articles mention no released exploit code or repository, so working exploit code appears not to be public, though the technical write-ups are. Since the bypass is demonstrated and reproducible, updating managed Apple devices remains advisable.

Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 11:15.

Detalhes técnicos

  • The flaw sits in audiomxd, which runs the server side of AURemoteIO, the low-latency recording audio unit.
  • The handler for property 2009 (AUIOServer_SetProperty) copied an application-supplied 32-byte audit token into the client object. It never checked the kernel-supplied caller token, and it required no entitlement or code-signing check.
  • AQIONodeClient::SetCanRecord() grants recording without consulting TCC when the stored token's PID and process version match audiomxd's own. An app could therefore forge a token that identifies it as audiomxd.
  • The logs attributed the recording to the daemon, so they showed no app using the microphone.
  • The permission prompt appeared only on first launch. Declining it did not stop recording, and it did not reappear on later launches.
  • Meta's demo video was filmed on a later build that appears to have restored the indicator, so the missing dot applies only to the earlier build.
  • Calap reproduced it on iOS 26.6 and an iPadOS 27 beta with sandboxed test apps that had no added entitlements and only NSMicrophoneUsageDescription. Recording continued in the background and with the device locked (UIBackgroundModes = audio). The apps were installed from Xcode and never went through App Review, so App Review's effect is untested. Testing on macOS, tvOS, watchOS and visionOS is not reported (thehackernews.com).

Detalhes da correção

Meta's timeline says the fix shipped in iOS 27.0 beta 5 on 10 August 2026 (thehackernews.com). Apple shipped it on 17 August 2026 in iOS 26.6.1, iPadOS 26.6.1 and macOS Tahoe 26.6.2, on 14 September in macOS Sequoia 15.8, tvOS 27, watchOS 27 and visionOS 27, and on 26 October in iOS 18.7.11 and iPadOS 18.7.11 (iPhone XS, XS Max, XR, iPad 7th generation). The iOS 27 release notes do not list the flaw. The fix makes the service check the real caller identity supplied by the kernel. Outside callers now need the private entitlement com.apple.private.audio.client-audit-token-override, which an app cannot grant itself (thehackernews.com).

Remediação

  • Update to the patched releases listed above; no setting blocks the bypass (thehackernews.com).
  • Review untrusted apps on managed Apple devices.
  • No method is known to check whether an app recorded audio before the fix (thehackernews.com).

Linha do tempo

  1. thehackernews.com ↗ · pub. 17/11/2026 09:14 · coletado 17/11 11:00

    Apple audiomxd flaw CVE-2026-65339 let iPhone apps record audio after microphone permission was denied; patched across Apple OSes

    The article adds fixes on more platforms and branches: iOS/iPadOS 18.7.11 (Oct 26), macOS Sequoia 15.8, tvOS 27, watchOS 27 and visionOS 27 (Sep 14). It also adds CISA's CVSS 5.0 and its absence from KEV, Calap's test conditions (foreground start, background and locked-device recording, Xcode-installed apps), and the new entitlement check in the fix.

    ler a análise desta fonte

    The article adds fixes on more platforms and branches: iOS/iPadOS 18.7.11 (Oct 26), macOS Sequoia 15.8, tvOS 27, watchOS 27 and visionOS 27 (Sep 14). It also adds CISA's CVSS 5.0 and its absence from KEV, Calap's test conditions (foreground start, background and locked-device recording, Xcode-installed apps), and the new entitlement check in the fix.

    A now-patched flaw in Apple's audio service (audiomxd), tracked as CVE-2026-65339, let apps on iPhones and iPads record microphone audio after the user tapped "Don't Allow". Nik Tsytsarkin of Meta Red Team X published technical details, and Mustafa Calap reported the same flaw separately. Neither Apple nor the researchers report exploitation, and CISA's KEV catalog does not list it. CISA rates it CVSS 5.0. The test apps had to be installed on the device already, and recording had to start in the foreground. Apple's notes describe it only as an app that may leak sensitive user information.

    Technical Details

    • audiomxd accepted the app-supplied audit token as the caller's identity. An app could send a token naming audiomxd itself, so the service took an internal shortcut and recorded without asking TCC.
    • Logs named the audio service as the recorder. On an earlier build the orange indicator stayed off. The demo video was filmed on a later build that appears to have restored it.
    • Calap reproduced it on iOS 26.6 and an iPadOS 27 beta. His apps were sandboxed, had no added entitlements, and used only NSMicrophoneUsageDescription. Recording continued in the background and with the device locked (UIBackgroundModes = audio).
    • Both apps were installed from Xcode and never went through App Review, so it is unknown whether App Review would have stopped them.
    • The bypass covered only microphone capture and gave no other permissions. macOS, tvOS, watchOS and visionOS were not reported as tested.

    Fix Details

    The fix makes the service check the real caller identity supplied by the kernel. Outside callers now need the private entitlement com.apple.private.audio.client-audit-token-override. Meta's timeline says it shipped in iOS 27.0 beta 5 on August 10. No pull request is applicable.

    Remediation

    • Install the fixed releases: iOS/iPadOS 26.6.1 (Aug 17), iOS/iPadOS 18.7.11 (Oct 26), macOS Tahoe 26.6.2 (Aug 17), macOS Sequoia 15.8 (Sep 14), tvOS 27, watchOS 27 and visionOS 27 (Sep 14).
    • No setting blocks the bypass, and no way is known to check whether an app recorded before the fix.
  2. gbhackers.com ↗ · pub. 16/11/2026 08:42 · coletado 16/11 10:00 primeiro registro

    Apple audiomxd flaw CVE-2026-65339 lets sandboxed apps record microphone audio without TCC permission

    ler a análise desta fonte

    A flaw in Apple's audio media daemon (audiomxd), tracked as CVE-2026-65339, let a sandboxed app record microphone audio without user permission. On an earlier build it also hid the orange privacy indicator. Meta Red Team X researcher Nik Tsytsarkin disclosed it and also credited Mustafa Calap. Apple's advisory describes it only as an Audio issue where an app may leak sensitive user information. Apple fixed it in iOS 26.6.1, iPadOS 26.6.1 and macOS Tahoe 26.6.2. The article does not report exploitation in the wild. It is a local flaw: the attacker needs an app already running on the device. The bypass covers only microphone capture through this audio path and does not grant general TCC permissions. This summary comes from the article alone, because no web research was done.

    Technical Details

    • The flaw sits in audiomxd, which runs the server side of AURemoteIO, the low-latency recording audio unit.
    • The handler for property 2009 (AUIOServer_SetProperty) copied an application-supplied 32-byte audit token into the client object. It never checked the kernel-supplied caller token, and it required no entitlement or code-signing check.
    • AQIONodeClient::SetCanRecord() grants recording without consulting TCC when the stored token's PID and process version match audiomxd's own. An app could therefore forge a token that identifies it as audiomxd.
    • The logs attributed the recording to the daemon, so they showed no app using the microphone.
    • The permission prompt appeared only on first launch. Declining it did not stop recording, and it did not reappear on later launches.
    • Meta's demo video was filmed on a later build that appears to have restored the indicator, so the missing dot applies only to the earlier build.

    Fix Details

    Apple fixed the issue on 10 August 2026 in iOS 27.0 beta 5. It shipped the fix on 17 August 2026 in iOS 26.6.1, iPadOS 26.6.1 and macOS Tahoe 26.6.2. The article does not describe the code change.

    Remediation

    • Update to the patched releases.
    • Review untrusted apps on managed Apple devices.