Skip to content
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report
FrameFrame home

Your digital life. Back in your hands.

100% Canadian-owned · Support: support@frameprivacy.com

Product

  • Platform
  • Sample report
  • Breach Check
  • Frame agent
  • Extension
  • Mobile app
  • Pricing
  • Frame Business
  • Changelog

Resources

  • Blog
  • Help centre
  • Free leak test
  • Status
  • Data-broker catalog
  • RSS feed

Company

  • About
  • Our privacy promise
  • Contact
  • Press and brand

Legal

  • Legal hub
  • Privacy Policy
  • Terms
  • Security
  • Cookies
  • Accessibility

© 2026 Frame Labs Inc. All rights reserved.

en Englishfr Français
Your Privacy ChoicesSystem status

All posts

Research · 5 min read

Researchers show an iPhone app could record after you tapped “Don’t Allow”. It’s fixed

Two researchers detail CVE-2026-65339, a flaw in Apple’s audio service that let an installed app capture the microphone without permission. Apple patched it in August. No attacks have been reported.

BBy Brody · FramePublished November 17, 2026
The Apple logo on a light card, joined by a dotted arrow to an orange tile with a crossed-out microphone icon, on a dark background.

When an iPhone app asks for the microphone and you tap "Don’t Allow", that answer is supposed to stick. Two researchers have now published how, before a fix Apple shipped in August, an app could keep recording anyway. The flaw is CVE-2026-65339. Nik Tsytsarkin of Meta Red Team X published his technical write-up on November 9, 2026, and Mustafa Calap, who found the same bug on his own, published his analysis the same day. The Hacker News brought the two together on November 17.

The short version for most people: it is patched, it needed an app already installed on the device, and neither Apple nor the researchers report that it was used in attacks. Updating is the fix.

What the researchers showed

Both researchers describe the same mistake in Apple’s audio service, a background process the write-ups call audiomxd. Apps do not decide for themselves whether they may record. The system checks with Apple’s permission service, Transparency, Consent, and Control (TCC), and that check depends on knowing which process is asking.

The audio service accepted an identity value that the app itself supplied, through an undocumented setting. An app could hand over the audio service’s own identity. The service then believed the request came from itself, took a shortcut meant for its own internal audio, and allowed recording without asking TCC. Calap writes that the app can get the audio service’s identity details from the system just by asking it a simple question, so nothing had to be guessed.

What the two write-ups demonstrate:

  • Recording after a refusal. In Tsytsarkin’s tests the prompt appeared on first launch, declining it did not stop recording, and the prompt did not come back. Calap’s test app recorded while its permission still read "denied".
  • No orange dot, on some builds. On the earlier test build Tsytsarkin analyzed, the orange microphone indicator stayed off and the system logs credited the recording to the audio service, not the app. His demo video was filmed on a later build where the dot does appear, and he says so. Calap says no indicator appeared in the Dynamic Island or Control Center in his test.
  • Recording kept going in the background. In Calap’s tests recording had to start while the app was on screen, then continued after it went to the background and after the device was locked.

Calap reproduced it on iOS 26.6 and an iPadOS 27 beta. His test apps were ordinary sandboxed apps with no special entitlements, installed from Xcode.

What was not shown

The researchers are careful about the limits, and they matter:

  • No reported attacks. Neither write-up reports the flaw being used against real people. Apple’s security notes for this CVE do not say it was exploited.
  • App Review was not tested. The test apps were installed directly from Xcode and never went through the App Store. So the research does not show whether Apple’s review would have caught an app doing this.
  • Microphone only. Tsytsarkin says the bypass covered microphone capture through this one audio path. It did not give the app other permissions.
  • No way to check the past. Neither researcher describes a way for you to tell whether an app recorded you before the fix.

What Apple fixed, and where

Apple’s notes describe the issue only as "An app may be able to leak sensitive user information" and "A logic issue was addressed with improved checks." Tsytsarkin writes that this leaves out the most striking part. The fix, per his write-up, makes the audio service rely on the real caller identity that the system supplies.

The fix is in:

  • iOS 26.6.1 and iPadOS 26.6.1 (August 17), for iPhone 11 and later and supported iPads
  • iOS 18.7.11 and iPadOS 18.7.11 (October 26), for iPhone XS, XS Max, XR and iPad 7th generation
  • macOS Tahoe 26.6.2 and macOS Sequoia 15.8
  • tvOS 27, watchOS 27 and visionOS 27

Tsytsarkin’s timeline says iOS 27 carried the fix from beta 5 on August 10. Apple’s iOS 27 notes do not list this CVE, and Calap notes that Apple added his name to the advisories on September 14, after first crediting only Tsytsarkin.

What you can do

  1. Update. On an iPhone or iPad, go to Settings, then General, then Software Update. Any of the versions above, or iOS 27, includes the fix. The researchers describe no setting that blocks the bug, so the update is the fix.
  2. Look at who has the microphone. In Settings, then Privacy & Security, then Microphone, turn off apps that do not need it. That list is what the fixed system enforces.
  3. Keep an eye on the orange dot. On a patched device it is a good signal again. If it lights up when you are not using the microphone, open Control Center to see which app is using it.
  4. Install apps from people you trust. This bug needed an app already on the device. Fewer unknown apps means fewer chances for the next one.
  5. Older devices count too. If someone in your family still uses an iPhone XS or XR, iOS 18.7.11 is their fix.

How Frame helps

This is a phone permission bug, not a breach of your personal information, so there is nothing new to look up today. Frame can also look up your verified emails in Have I Been Pwned’s breach database whenever you want to check what has leaked. Frame doesn’t scan your phone or your apps.

Related coverage

  • Apple is tightening Full Disk Access on the Mac. Check which apps have it today: the same idea on the Mac, and how to review which apps have a powerful permission.
  • iVerify says criminals, not governments, now cause most of the iPhone spyware it finds: why keeping an iPhone updated matters for ordinary people, not only for targets.

Sources

  • Nik Tsytsarkin, Meta Red Team X, Who needs permissions and the orange dot that never lit, November 9, 2026
  • Mustafa Calap, CVE-2026-65339: A Microphone Permission Bypass on iOS, November 9, 2026
  • Apple, About the security content of iOS 26.6.1 and iPadOS 26.6.1
  • Apple, About the security content of iOS 18.7.11 and iPadOS 18.7.11
  • Apple, About the security content of macOS Tahoe 26.6.2
  • The Hacker News, Researchers Detail iPhone Flaw That Let Apps Record Audio Despite Denied Microphone Permission, November 17, 2026
  • Research
  • Guides
More in Research

More stories

  • MalwareUnit 42 says two quiet tools have been spying on government networksNovember 17, 2026 · 4 min read
  • MalwareKaspersky describes backdoors that hide inside SharePoint, GitHub and AblyNovember 17, 2026 · 4 min read
  • ResearchProject Zero is shortening the time vendors get before a bug is publishedNovember 17, 2026 · 5 min read

New posts, by email.

About once a month. Plain-language privacy notes, nothing else. I never share your address.

Sent by Frame · privacy@frameprivacy.com · Privacy Policy

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report
FrameFrame home
PlatformBreach CheckFrame agentExtensionPrivacyBusinessPricing
Sign inSample report

See what’s exposed about you.

Frame is in private beta. See what it finds, and how it helps you take it down, in a sample report built from made-up data.

See a sample exposure report