Apple macOS CVE-2026-86935

Exploitation requires the attacker's code to already be running locally as an application on the macOS host (AV:L) - i.e., a malicious or compromised app must be installed and executed; there is no remote, network-facing vector. The flaw stems from the app being granted additional entitlements it should not have had, which the fix removes, so exploitation is tied to that entitlement misconfiguration in versions before macOS Golden Gate 27. Limiting factors: local code execution is a prerequisite, impact is confined to disclosure of user-sensitive data (no integrity or availability impact), and updating to macOS Golden Gate 27 is the vendor's stated remediation. The specific entitlement, feature, or data category involved is not detailed in the available sources.

This is a moderate-severity local information-disclosure issue in Apple macOS, and the available signals are consistent rather than conflicting. The supplied CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 5.5) describes a local attack with low complexity, no user interaction, a high confidentiality impact and no integrity or availability impact - a read-only exposure of user-sensitive data, not code execution or system takeover. EPSS is very low (0.14%, 3rd percentile) and the CVE is NOT on CISA KEV, so there is no indication of active or imminent widespread exploitation; no SSVC decision block or POC reference is present in the input. The vendor (Apple) is the reporter, a patch is available, and vuln.today assigns a 'this_month' priority rather than an emergency. Net assessment: a genuine but non-urgent privacy/confidentiality fix - prioritize for routine monthly patching, not emergency response. No SSVC automatable/technical-impact fields were provided, so the decision rests on CVSS plus the low EPSS and absent KEV.

A user installs or is tricked into running a malicious or compromised application on macOS; because of the extra entitlements that were removed in the fix, that app reads user-sensitive data it should not be able to reach. No public exploit or PoC is identified in the provided data, and because AV:L/AC:L the attack is local and low-complexity but requires the attacker's code to already be executing on the machine.