Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-84589-macOS-TCC-Bypass — CVE-2026-84589: macOS TCC privacy bypass via FaceTime impersonation. Technical PoC analysis, Apple disclosure timeline, and patch coverage. | Kitploit
Tools/GitHubGitHub/isaiahehlert/cve-2026-84589-macos-tcc-bypass
Privilege EscalationVulnerability AnalysisPapers & ResearchLearning & Education
GitHubisaiahehlert/cve-2026-84589-macos-tcc-bypass

CVE-2026-84589-macOS-TCC-Bypass

CVE-2026-84589: macOS TCC privacy bypass via FaceTime impersonation. Technical PoC analysis, Apple disclosure timeline, and patch coverage.

View Repository
Share
125 days agoNot yet reviewed

CVE-2026-84589 — macOS TCC Privacy Preferences Integrity

Security research and coordinated disclosure by Isaiah Ryan Ehlert | Sentinel Research Group

Apple's published impact: An app may be able to modify Privacy preferences. Apple states that additional restrictions addressed the TCC permissions issue in macOS Golden Gate 27.

FieldDetails
CVECVE-2026-84589
ComponentmacOS Transparency, Consent, and Control (TCC)
Original Apple submissionOE1102329983018
Date I first reported the issueMay 8, 2025
Publicly documented fixmacOS Golden Gate 27 — September 14, 2026
Reporting-to-release interval494 days (1 year, 4 months, 6 days)
Test environmentmacOS Sequoia 15.5, including a Mac mini M4 with SIP enabled
Research creditApple credits multiple researchers, including me; I do not claim exclusive discovery.

Executive summary

I investigated a trust boundary in macOS's Transparency, Consent, and Control (TCC) subsystem: how privacy permissions are associated with an application's identity and how those decisions are enforced when an application presents itself as a trusted system app.

For my proof of concept, I created a test application that presented FaceTime's bundle identity. In one controlled test sequence, I modified relevant TCC authorization records and then launched my app. Camera access proceeded without a new permission prompt, while macOS displayed FaceTime in Privacy settings even though I had launched my test application. I documented my findings and provided supporting evidence to Apple Product Security.

This is an important qualification: the controlled sequence involved prior TCC state modification. I also explored test variations with different prerequisites. I am not representing every variation as an unconditional, permissionless exploit.

Apple's confirmed public finding is narrower than my full research record. Apple's advisory credits me alongside other researchers for CVE-2026-84589 and describes an issue allowing an app to modify Privacy preferences. The advisory does not establish every camera, keychain, cloud, or entitlement-related hypothesis I investigated separately.

How the issue worked

My research focused on the relationship among three elements:

  1. Application identity: Metadata identifying my test application as FaceTime.
  2. TCC permission state: Records indicating whether a privacy-protected capability was authorized.
  3. Runtime enforcement: The actual executable requesting camera access and the identity shown to the user.

The behavior I observed raised a question about whether privacy authorization was being reliably associated with the correct executable. An app's name or bundle identifier should not, on its own, replace the integrity checks needed to enforce user consent. That is my technical interpretation; Apple has not published a complete root-cause analysis for this CVE.

My documented PoC concerns a local TCC privacy-integrity issue. I am not claiming I demonstrated remote initial access, zero-click compromise, or universal inheritance of Apple-only entitlements.

Read my Technical Analysis for test conditions, observations, prerequisites, and limits.

Reporting and patch timeline

I submitted the original report to Apple on May 8, 2025. Apple publicly released macOS Golden Gate 27 on September 14, 2026, including CVE-2026-84589 in the security advisory.

That is 494 days between my report and public availability of the documented fix. I do not know when Apple internally completed engineering work, and I do not present this interval as engineering time.

See my Disclosure Timeline for dated milestones from my private case record.

Earlier macOS releases

I reviewed Apple's security advisories for releases issued alongside macOS 27. CVE-2026-84589 was not listed in the release-day security contents for macOS Tahoe 26.7 or macOS Sequoia 15.8; Apple documents the CVE-specific fix for macOS Golden Gate 27.

Apple's affected-version information describes macOS releases earlier than 27 as affected. However, I have not independently reproduced my original PoC on every earlier build or published a post-release differential test. The missing advisory entries are not, by themselves, proof that the same technique works unchanged on each older release.

See Patch Coverage.

Publication scope

I am publishing my research narrative and technical analysis, not an exploit kit. I have kept the original binaries, detailed exploit instructions, raw logs, personal or authentication data, and private correspondence with Apple out of this public repository.

My separate FaceTime/iCloud investigation remains private and is not part of this CVE disclosure.

Research credit

Apple's public acknowledgement names an anonymous researcher, Rodolphe Brunetti, Ryan Dowd, me (Isaiah Ryan Ehlert), and Csaba Fitzl. I acknowledge the other credited researchers and do not claim that I was the only person to discover or report the issue.

This is my independent research publication. It is not affiliated with or endorsed by Apple.

Primary references

  • Apple: Security content of macOS Golden Gate 27
  • Apple: Security content of macOS Tahoe 26.7
  • Apple: Security content of macOS Sequoia 15.8
  • NVD: CVE-2026-84589

Copyright © 2026 Isaiah Ryan Ehlert. Reproduction for education and news reporting is permitted subject to my custom license. Other rights reserved. See also Reuse Policy.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    977
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    564
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    352
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    344
  • 5

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    322
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    308

Explore all tools

Browse our collection of tools

View all tools →