The Hacker News reports iPhone flaw let apps record audio after mic denied
The Hacker News reports researchers detail a patched iOS flaw that let apps record audio after microphone denial; install Apple’s updates.
- Published
- Ecosystem
- Desktops, browsers and mobile
- Fixed in
- iOS 26.6.1 and iPadOS 26.6.1, iOS 18.7.11 and iPadOS 18.7.11, macOS Tahoe 26.6.2, macOS Sequoia 15.8, tvOS 27, watchOS 27, visionOS 27
- Exploitation
- No. According to The Hacker News, neither Apple nor the two researchers report use in attacks, and CISA’s known exploited catalog did not list it as of its latest update.
Live scores
CVE-2026-65339- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.510
likely exploited - On CISA KEV
- Not listed
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
What happened
The Hacker News reports that a now-patched flaw in Apple’s audio service let apps on iPhones and iPads record audio even after the user tapped “Don’t Allow” on the microphone prompt The Hacker News. This advisory rests on that single outlet. No Apple advisory or official CVE record was among the sources, so everything below is the outlet’s account of the researchers’ work.
According to The Hacker News, Nik Tsytsarkin of Meta Red Team X published technical details last week, and Mustafa Calap, a security engineer who reported the same flaw separately, published his own analysis the same day The Hacker News. The outlet says the flaw is tracked as CVE-2026-65339. We did not have an official record for that ID, so its details are not independently confirmed here.
The outlet says the audio service, called audiomxd, accepted the app’s own claim about which process was asking for microphone access. An app could send a token naming audiomxd itself, so the service used an internal shortcut and allowed recording without asking the Transparency, Consent, and Control (TCC) system. The outlet says the fix makes the service check the real caller’s 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 The Hacker News.
What the outlet reports about behavior in the researchers’ tests:
- The orange microphone indicator stayed off on one earlier test build. Tsytsarkin’s demo video was filmed on a later build that appears to have restored it.
- Calap’s test app recorded while its permission still read denied, with no indicator in the Dynamic Island or Control Center. He does not say which of his two builds that was.
- Recording had to start in the foreground. It then continued after the app went to the background and after the device was locked.
- The test apps were installed from Xcode and never went through App Review.
According to The Hacker News, the first fixed updates came out on August 17. The outlet says CISA gives the flaw a CVSS score of 5.0 out of 10, and that Apple’s notes describe the issue only as one that may let an app leak sensitive user information The Hacker News.
What is not confirmed: any exploitation in the wild (the outlet says neither Apple nor the researchers report it), whether App Review would have stopped such an app, and any behavior on macOS, tvOS, watchOS or visionOS, which neither researcher reports testing.
Am I affected?
According to The Hacker News, the bypass needed an app already installed on the device. It covered microphone capture through the audio service only and did not grant other privacy permissions. Calap reproduced it on iOS 26.6 and on an iPadOS 27 beta, and the Meta analysis compared two iOS 27 test builds The Hacker News.
The outlet lists fixes for these releases:
- iOS 26.6.1 and iPadOS 26.6.1 (August 17), for iPhone 11 and later and several iPad generations
- iOS 18.7.11 and iPadOS 18.7.11 (October 26), for iPhone XS, iPhone XS Max, iPhone XR and iPad 7th generation
- macOS Tahoe 26.6.2 (August 17)
- macOS Sequoia 15.8 (September 14)
- tvOS 27, watchOS 27 and visionOS 27 (September 14)
The outlet says neither researcher describes a way to check whether an app recorded a user before the fix. It also says the iOS 27 release notes do not list the flaw, while Meta’s timeline says the fix shipped in iOS 27.0 beta 5 on August 10 The Hacker News. Whether a particular public iOS 27 build contains the fix is therefore not confirmed in the source.
What to do now
- Check your device’s software version in Settings and compare it with the fixed releases above.
- Install the available Apple update for your device. The Hacker News says the researchers describe no setting that blocks the bypass, so updating is the fix.
- If you run iOS 27, note that the source does not confirm which public build includes the fix. Check Apple’s own security notes for your version.