A Microphone Permission Bypass on iOS 26 (CVE-2026-65339)
Comments on “A Microphone Permission Bypass on iOS 26 (CVE-2026-65339)”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A researcher details CVE-2026-65339, a flaw in iOS 26 and related Apple systems that let a sandboxed app with no special entitlements record microphone audio after the user denies permission.
Why it ranked
No. 22 of 95 with a score of 0.70. The panel rated it highest on technical depth (0.96) and substantiated (0.91), lowest on audience breadth (0.53). Placed No. 22, No. 9 by score alone: the eighth Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, reproducible security write-up of a privacy-consent bypass in iOS audio daemon with code and disclosure timeline; highly technical and relevant to security-minded builders, though narrow to Apple platform developers.}
- AI judgeJudge 3gpt-5.6-luna
- A highly technical, reproducible iOS microphone-permission bypass analysis, supported by disassembly, proof-of-concept code, build comparisons, and remediation details. It is directly relevant to mobile security and privacy, though narrower than general technology news.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.70total under rubric v2.3
- Significance0.66
- Reader interest0.83
- Audience breadth0.53
- Practical relevance0.62
- Substantiated0.91
- Technical depth0.96
- New information0.90
- Counts against: Promotional0.03
- Counts against: Overclaim0.15
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.56 | 0.60 | 0.83 | 0.66 | 0.27 | +0.24 | +0.159 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.69 | 0.85 | 0.94 | 0.83 | 0.25 | +0.26 | +0.215 |
| Audience breadthHow many people who build technology does it concern? | 0.43 | 0.60 | 0.56 | 0.53 | 0.17 | +0.13 | +0.069 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.65 | 0.45 | 0.76 | 0.62 | 0.31 | +0.22 | +0.136 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.96 | 0.85 | 0.91 | 0.91 | 0.11 | +0.05 | +0.045 |
| Technical depthHow technically substantive is it? | 1.00 | 0.90 | 0.97 | 0.96 | 0.10 | +0.05 | +0.048 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.85 | 0.97 | 0.90 | 0.12 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.03 | 0.01 | 0.03 | 0.03 | −0.19 | −0.005 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.24 | 0.15 | 0.06 | 0.15 | 0.18 | −0.11 | −0.017 |
| Sum of contributions | +0.696 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.696 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-10/22/"><img src="https://rubric.hrih.si/badge/2026-11-10/22.svg" alt="Ranked #22 on Rubric, 10 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 no source given · 6 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkVersion
The iOS 26.6.1 fix requires the entitlement com.apple.private.audio.client-audit-token-override for the audit-token property write, otherwise it fails with kAudioUnitErr_Unauthorized.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Unless the sender token is the all-0xFF _gBogusAuditToken sentinel, it now requires this entitlement”
The source says No passage could be compared.
Source cited by the article: updates.cdn-apple.com/2026SummerFCS/fullrestores/140-74072/E64E64AC-7C84-4950-95FA-7AF8A43CBC64/iPhone16,2_26.6.1_23G83_Restore.ipsw
Couldn’t checkVersion
The vulnerability was reproduced on iPadOS 27.0 beta 24A5390f and iOS 26.6 23G71, and fixed in iOS and iPadOS 26.6.1 and macOS Tahoe 26.6.2.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Fixed in iOS and iPadOS 26.6.1, macOS Tahoe 26.6.2 and the later releases below”
The source says No passage could be compared.
Source cited by the article: support.apple.com/en-us/148282
Couldn’t checkDate
Apple's 17 August advisories for CVE-2026-65339 initially credited Nik Tsytsarkin of Meta Red Team X, and Apple added the author's name on 14 September.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The 17 August advisories initially credited Nik Tsytsarkin of Meta Red Team X, and Apple added my name to them on 14 September”
The source says No passage could be compared.
Source cited by the article: support.apple.com/en-us/148282
Couldn’t checkNumber
A Ravel entitlement search finds only one holder of the new entitlement, /usr/libexec/cameracaptured.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “An entitlement search there finds one holder, /usr/libexec/cameracaptured”
The source says No passage could be compared.
Source cited by the article: ravel.dbg.re/search
Couldn’t checkNumber
The Ravel diff of AudioToolbox from 26.6 to 26.6.1 adds four strings: the entitlement, a rejection line for each path and a new build stamp.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “adds four strings: the entitlement, a rejection line for each path and a new build stamp”
The source says No passage could be compared.
Source cited by the article: ravel.dbg.re/diff
Couldn’t checkVersion
The unguarded setter is still present in the 13 July beta 5 (23G5065a) but the entitlement check is not in the 23G71 AudioToolbox.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “None of this is in the 23G71 AudioToolbox, and the 13 July beta 5, 23G5065a, still has the unguarded code shown above”
The source says No passage could be compared.
Source cited by the article: updates.cdn-apple.com/2026SpringSeed/fullrestores/140-44745/3CEDAD7B-97D0-483C-A1D8-636127ADED04/iPhone16,2_26.6_23G5065a_Restore.ipsw
No source givenCausal conclusion
Apple said the issue was fixed before the author's report, in the 13 July iOS 26.6 beta, and found no security issue in the submission.
The article gives no link or citation for it.
The article says “Apple said the issue was fixed before my report, in the 13 July iOS 26.6 beta, and found no security issue in what I sent”
The source says No source to compare with.
No source givenCausal conclusion
Sending a property 2009 write with the audio daemon's audit token makes audiomxd treat the app as itself, so a denied app receives real microphone samples while its permission still reads denied.
The article gives no link or citation for it.
The article says “Told I am audiomxd, audiomxd decides the client is itself and sends it real microphone samples”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 6 pts, not on front page
Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.