Race Against the (Mac)Hine: Local Priv Esc in Microsoft Defender for macOS
Comments on “Race Against the (Mac)Hine: Local Priv Esc in Microsoft Defender for macOS”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A security researcher documents two local privilege escalation bugs in Microsoft Defender for macOS, CVE-2026-50657 (arbitrary file read) and CVE-2026-50658 (a TOCTOU race), which are macOS variants of Windows flaws patched earlier in 2026.
Why it ranked
No. 24 of 122 with a score of 0.69. The panel rated it highest on technical depth (0.97) and new information (0.92), lowest on audience breadth (0.45). Placed No. 24, No. 15 by score alone: the tenth 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, well-evidenced macOS privilege-escalation writeup in Defender with PoC-level technical depth; highly relevant to security audiences, narrower in audience breadth, and not overclaimed.
- AI judgeJudge 3gpt-5.6-luna
- A highly technical, detailed vulnerability writeup with exploit mechanics, macOS security analysis, CVEs, and remediation guidance. It is directly valuable to security engineers, though its primary impact is within macOS and privileged IPC work.
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.69total under rubric v2.3
- Significance0.60
- Reader interest0.82
- Audience breadth0.45
- Practical relevance0.71
- Substantiated0.84
- Technical depth0.97
- New information0.92
- 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.45 | 0.78 | 0.60 | 0.33 | +0.24 | +0.144 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.71 | 0.80 | 0.95 | 0.82 | 0.24 | +0.26 | +0.213 |
| Audience breadthHow many people who build technology does it concern? | 0.41 | 0.40 | 0.55 | 0.45 | 0.15 | +0.13 | +0.059 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.70 | 0.60 | 0.82 | 0.71 | 0.22 | +0.22 | +0.156 |
| 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.80 | 0.85 | 0.88 | 0.84 | 0.08 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 1.00 | 0.92 | 0.98 | 0.97 | 0.08 | +0.05 | +0.048 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.90 | 0.95 | 0.92 | 0.05 | +0.05 | +0.046 |
| 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.03 | 0.03 | 0.02 | 0.03 | 0.01 | −0.19 | −0.005 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.19 | 0.15 | 0.12 | 0.15 | 0.07 | −0.11 | −0.017 |
| Sum of contributions | +0.686 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.686 | ||||||
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-17/24/"><img src="https://rubric.hrih.si/badge/2026-11-17/24.svg" alt="Ranked #24 on Rubric, 17 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 5 no source given · 3 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Microsoft patched both macOS Defender vulnerabilities, assigning CVE-2026-50657 (arbitrary file read) and CVE-2026-50658 (TOCTOU race condition / elevation of privilege).
The article gives no link or citation for it.
The article says “Microsoft has since patched both, assigning CVE-2026-50657 (arbitrary file read / information disclosure) and CVE-2026-50658 (TOCTOU race condition / elevation of privilege”
The source says No source to compare with.
No source givenDate
Both bugs were reported to MSRC and fixed in the July 2026 Patch Tuesday.
The article gives no link or citation for it.
The article says “Both bugs were reported to the Microsoft Security Response Center (MSRC) and fixed on the July 2026 Patch Tuesday”
The source says No source to compare with.
Couldn’t checkDate
Samuel Groß presented the "PID reuse" technique in his "Don't Trust the PID!" WarCon 2018 talk.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “This “PID reuse” technique was presented by Samuel Groß (5aelo) in his Don’t Trust the PID! WarCon 2018 talk”
The source says No passage could be compared.
Source cited by the article: saelo.github.io/presentations/warcon18_dont_trust_the_pid.pdf
Couldn’t checkDate
Windows hardlinks have required FILE_WRITE_ATTRIBUTES access to the target since 2015, as James Forshaw documented.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Unlike a Windows hardlink, which has required FILE_WRITE_ATTRIBUTES access to the target since 2015, as James Forshaw documented in Between a Rock and a Hard Link”
The source says No passage could be compared.
Source cited by the article: projectzero.google/2015/12/between-rock-and-hard-link.html
No source givenNumber
Defender's wdavdaemon exposes two AF_UNIX sockets created mode 0666 and owned by root, so any local process can connect to them.
The article gives no link or citation for it.
The article says “Both are created mode 0666 (srw-rw-rw-), owned by root, so any local process may connect to them”
The source says No source to compare with.
No source givenCausal conclusion
The get_diagnostic_files opcode (0x0f) does not go through the AuthorizationCopyRights gate, giving an arbitrary file read as root.
The article gives no link or citation for it.
The article says “0x0f get_diagnostic_files does not funnel through the AuthorizationCopyRights gate at all”
The source says No source to compare with.
Couldn’t checkFirst, only or fastest
The audit token is the only peer credential that is both bound to a specific process and invalidated when that process re-execs.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “It is the only peer credential that is both bound to a specific process and invalidated when that process re-execs”
The source says No passage could be compared.
Source cited by the article: knight.sc/reverse%20engineering/2020/03/20/audit-tokens-explained.html
No source givenGeneralization
Patching the same primitives on Windows is not sufficient to secure them on macOS, because of OS differences.
The article gives no link or citation for it.
The article says “Because of these differences, patching the same primitives on Windows is not sufficient to secure them on macOS”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.