VulnerabilityPublished 11 Feb 2026Updated 2 Apr 2026

CVE-2026-20624: Apple macOS · Incorrect Authorization

Affects Apple macOSSource CVE Database V5

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

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 26.3, 15.7.4, 14.8.4

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 11 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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.3, 15.7.4 or 14.8.4.

Affected software

Product	Affected	Fixed in
ApplemacOS	Affected <26.3	Fixed in 26.3
ApplemacOS	Affected <15.7.4	Fixed in 15.7.4
ApplemacOS	Affected <14.8.4	Fixed in 14.8.4

AI-suggested

To mitigate CVE-2026-20624, organizations should: 1) Immediately deploy the security updates released by Apple for macOS Sequoia 15.7.4, Sonoma 14.8.4, and Tahoe 26.3 or later versions. 2) Restrict local user permissions to minimize the ability to install or run untrusted applications. 3) Implement application whitelisting and endpoint protection solutions that can detect or block suspicious app behaviors. 4) Educate users to avoid executing unknown or untrusted applications, especially those requesting elevated privileges or access to sensitive data. 5) Monitor system logs and endpoint telemetry for unusual access patterns or attempts to exploit local vulnerabilities. 6) Employ network segmentation to limit lateral movement if a local compromise occurs. 7) Regularly audit installed software and user privileges to ensure compliance with least privilege principles. These steps go beyond generic patching by focusing on reducing attack surface and improving detection capabilities.

Description

An injection issue was addressed with improved validation. This issue is fixed in macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.3. An app may be able to access sensitive user data.

Impact

The primary impact of CVE-2026-20624 is unauthorized access to sensitive user data on affected macOS systems. This can lead to privacy breaches, exposure of personal or corporate confidential information, and potential compliance violations for organizations handling regulated data. Since the vulnerability does not affect integrity or availability, it does not allow data modification or system disruption, but the confidentiality breach alone can have serious consequences, including identity theft, corporate espionage, or targeted attacks leveraging stolen data. The requirement for local access and user interaction limits remote exploitation but does not eliminate risk, especially in environments where users may be tricked into running malicious apps or scripts. Organizations with macOS endpoints, particularly those in sectors like finance, healthcare, and government, face increased risk if patches are not applied promptly. The absence of known exploits reduces immediate threat but does not preclude future exploitation attempts.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (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, 02:50 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats