CVE-2025-43339: macOS Tahoe Sandbox Access Control Bypass Allows User Data Disclosure
A sandbox isolation weakness in macOS Tahoe allows a malicious app running with user privileges to read sensitive user data that should have been protected. The vulnerability does not allow the attacker to modify data or crash the system, only to view it. Apple has patched this in macOS Tahoe 26.1 by strengthening sandbox restrictions.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Weaknesses (CWE)
- CWE-284
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-11 / 2026-06-17
NVD description (verbatim)
An access issue was addressed with additional sandbox restrictions. This issue is fixed in macOS Tahoe 26.1. A malicious app may be able to access sensitive user data.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2025-43339 is an access control failure (CWE-284) in the macOS sandbox architecture. The vulnerability permits a locally-running malicious application to circumvent sandbox boundaries and access protected user data. The attack requires the app to already be executing on the system with user-level privileges; no elevation or interaction is needed to trigger the breach once the malicious app is present. The fix involves tightening sandbox restriction rules to prevent this data access path.
Business impact
For macOS users, this creates risk of unauthorized disclosure of personal information—potentially including documents, browsing history, authentication tokens, or other data stored in protected directories. Organizations deploying managed macOS fleets should treat this as a user-data confidentiality threat. The risk is elevated for users who install untrusted third-party applications, as such apps could exfiltrate sensitive information without the user's knowledge. However, the attack does not enable persistence, privilege escalation, or system compromise beyond data theft.
Affected systems
macOS Tahoe versions prior to 26.1. This vulnerability affects users running any earlier version of macOS Tahoe on Intel and Apple Silicon Macs.
Exploitability
Exploitability is local-only and requires a malicious app to already be running on the target system. There is no network attack surface, no requirement for user interaction beyond app installation, and no special privileges needed beyond standard user-level execution. The barrier to exploitation is primarily distribution and installation of the malicious app itself. Once running, the data access occurs without additional user prompts.
Remediation
Install macOS Tahoe 26.1 or later. This is a critical maintenance update and should be deployed promptly to all managed macOS systems, particularly in environments handling sensitive user data.
Patch guidance
Verify and deploy macOS Tahoe 26.1 from Apple's official Software Update mechanism. Test in a pre-production environment first, particularly for organizations with legacy applications or specific macOS configurations. For managed environments, use your mobile device management (MDM) solution to push the update. Apple typically provides security update details and known issues in release notes—review these before broad rollout to identify any compatibility concerns.
Detection guidance
Monitor system logs for sandbox policy violations or app permission denials that might indicate an app attempting to access restricted user data. Endpoint detection and response (EDR) tools should flag apps executing with unusual file-system access patterns, particularly access to user library directories, keychain, or browser profile folders. Network monitoring can help identify unusual data exfiltration attempts. However, the most reliable detection method is to ensure all Macs are running Tahoe 26.1 or later, reducing the attack surface to zero.
Why prioritize this
Although scored as MEDIUM severity, organizations should prioritize this patch because (1) it affects a fundamental trust boundary—the sandbox—that protects user data on every macOS system, (2) data theft is a primary business risk for any organization, (3) the exploit requires no special conditions once a malicious app is present, and (4) the fix is straightforward. Organizations heavy in macOS deployment or handling personally identifiable information should treat this as higher urgency.
Risk score, explained
CVSS 5.5 (MEDIUM) reflects the local-only attack vector, low attack complexity, and user-level privilege requirement. The high confidentiality impact (disclosure of user data) is offset by the lack of integrity or availability impact. The score appropriately captures a meaningful but contained risk—real for users of untrusted apps, less acute for organizations with app-control policies, but universally relevant to macOS security posture.
Frequently asked questions
Can this vulnerability be exploited remotely or over the network?
No. The attack is strictly local and requires malicious code to already be executing on the user's Mac. There is no network-based exploitation path.
Does this vulnerability allow an attacker to gain administrator access or install malware permanently?
No. CVE-2025-43339 allows read-only access to user data within the sandbox boundary. It does not provide privilege escalation, persistence, or the ability to modify system files or install persistence mechanisms.
What types of data are at risk if a malicious app exploits this?
Any user data that the sandbox was supposed to protect—this may include documents, photos, browser history, cookies, cached credentials, email, and other sensitive files stored in user directories. The exact scope depends on what the malicious app is designed to target.
Should I wait for an automatic update or manually update my Mac?
Enable automatic updates in System Preferences if not already active. If your organization manages your device, your IT department will push the update. For personal devices, check Software Update regularly and install Tahoe 26.1 as soon as it is available to you.
This analysis is based on official vulnerability data and Apple security advisories current as of the publish date. Specific patch versions, system compatibility, and deployment guidance should be verified against Apple's official Software Update service and security documentation. This vulnerability is theoretical until a malicious app is deployed; organizations with strict app-control policies face lower practical risk. SEC.co does not provide legal, compliance, or insurance advice; consult your organization's security governance framework for prioritization decisions. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2025-24165MEDIUMmacOS Permissions Issue Enables Unexpected System Termination
- CVE-2025-46308MEDIUMApple iOS, iPadOS, macOS Authorization Bypass—Sensitive Data Disclosure
- CVE-2026-11017MEDIUMChrome Link Preview Navigation Bypass (CVSS 6.5)
- CVE-2026-11026MEDIUMChrome Extension Navigation Bypass Vulnerability
- CVE-2026-11078MEDIUMChrome FileSystem Same-Origin Policy Bypass – MEDIUM Severity
- CVE-2026-11135MEDIUMChrome Autofill Bypass Allows Credential Misdirection
- CVE-2026-11187MEDIUMChrome Navigation Restriction Bypass Vulnerability
- CVE-2026-11190MEDIUMGoogle Chrome Extension Access Control Bypass (6.5 CVSS)