VulnerabilityPublished 25 Mar 2026Updated 2 Apr 2026

CVE-2026-20693: Apple macOS · Incorrect Permissions

Affects Apple macOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.9 Medium · fixed in 26.4 : update Apple macOS when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.4, 15.7.5, 14.8.5

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apple macOS to 26.4, 15.7.5 or 14.8.5.

Affected software

Product	Affected	Fixed in
ApplemacOS	Affected <26.4	Fixed in 26.4
ApplemacOS	Affected <15.7.5	Fixed in 15.7.5
ApplemacOS	Affected <14.8.5	Fixed in 14.8.5

AI-suggested

Apply the official Apple patches immediately by upgrading to macOS Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4 or later versions where the vulnerability is fixed.
Enforce strict access controls and monitoring on root accounts to prevent unauthorized root access.
Implement robust endpoint detection and response (EDR) solutions to detect suspicious activities involving system file deletions.
Regularly audit system file integrity using tools like Apple’s System Integrity Protection (SIP) and third-party file integrity monitoring solutions.
Limit the use of root privileges by employing the principle of least privilege and using sudo with logging enabled.
Educate administrators and users about the risks of privilege escalation and the importance of secure credential management.
Maintain up-to-date backups of critical systems to enable recovery in case of file deletion or system corruption.
Monitor security advisories from Apple and cybersecurity communities for any emerging exploit information or additional patches.

Description

This issue was addressed through improved state management. This issue is fixed in macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.4. An attacker with root privileges may be able to delete protected system files.

Impact

The primary impact of CVE-2026-20693 is on the integrity of affected macOS systems. An attacker with root privileges can delete critical system files that are normally protected, potentially causing system instability, malfunction, or denial of service. This could disrupt business operations, especially in environments relying on macOS for critical infrastructure or development. While confidentiality and availability are not directly impacted, the integrity compromise could facilitate further attacks or persistent system corruption. Since exploitation requires root access, the vulnerability mainly escalates damage potential after privilege escalation or insider threats. Organizations with macOS endpoints, especially those in enterprise, creative industries, or software development, could face operational risks if this vulnerability is exploited. The absence of known exploits reduces immediate risk but does not eliminate the threat, particularly in targeted attacks or advanced persistent threat scenarios.

CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 03:03 UTC

WeaknessesCWE-732

Technical details

References

Community reviews

Related threats