Breaking macOS App Sandbox Data Containers, TCC, and Hijacking Apps
A significant security vulnerability in macOS was discovered, allowing attackers to bypass App Sandbox protections. This flaw, linked to the Archive Utility, enables unauthorized access to sensitive files and the hijacking of third-party applications. Apple has addressed this issue in macOS version 26.4, but earlier versions remain at risk.
- ▪The vulnerability allows attackers to gain full access to files protected by macOS app data containers without triggering permission prompts.
- ▪Attackers can hijack third-party apps by replacing their executables, impersonating trusted applications.
- ▪The exploit requires only two user actions: running the attacker's code and dragging and dropping a specific file.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Mysk Blog – In-Depth Cybersecurity & Mobile App Privacy Research |
| Canonical URL | https://mysk.blog/2026/05/19/cve-2026-28910/ |
| Publication time | Fri, 29 May 2026 02:58:21 +0000 |
| Retrieval time | 2026-05-29T03:29:40.994Z |
| Last seen | 2026-05-29T03:29:40.994Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Sb2-zfINTkuS |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
CVE-2026-28910: Breaking macOS App Sandbox Data Containers, TCC, and Hijacking Apps Using Archive Utility 2026-05-19by Talal Haj Bakry and Tommy Mysk Until macOS 26.4, Archive Utility had nearly unrestricted filesystem access. Combined with a drag-and-drop sandbox quirk, this let an attacker bypass App Sandbox data containers, Transparency, Consent, and Control (TCC) protections, and hijack third-party apps — all without special permissions or elevated privileges. Table of Contents Affected Platforms Summary Summary for Non-Technical Readers Background A Quick Introduction to macOS App Sandbox and Data Containers Archive Utility’s (Nearly) Unrestricted Filesystem Access Drag & Drop: An Intentional Sandbox Loophole Unleashing Archive Utility Introducing au‑cp: Golden Copy Data Exfiltration…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Mysk Blog – In-Depth Cybersecurity & Mobile App Privacy Research.
Discussion
0 comments
