CVE-2025-43291VulnerabilityPublished 15 Sep 2025Updated 2 Apr 2026

CVE-2025-43291: Apple macOS · An app may be able to modify protected parts of the file system

Affects Apple macOSSource CVE Database V5

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

Data as of 26 Oct 2026, 08:30 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 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.7

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
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: 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 15 Sep 2025
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 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

Affected software

Product	Affected	Fixed in
Apple macOS	Affected =0	Fixed in–

AI-suggested

1. Immediately update all macOS systems to the patched versions: Sequoia 15.7, Sonoma 14.8, or Tahoe 26, as applicable. 2. Restrict installation of applications to trusted sources such as the Apple App Store or verified developers to reduce the risk of malicious apps exploiting this vulnerability. 3. Implement endpoint protection solutions capable of monitoring and blocking unauthorized attempts to modify protected file system areas. 4. Educate users about the risks of running untrusted applications and the importance of avoiding suspicious prompts that require interaction. 5. Employ application whitelisting and sandboxing to limit the capabilities of apps and prevent unauthorized file system modifications. 6. Regularly audit system integrity using file integrity monitoring tools to detect unauthorized changes to critical system files. 7. Enforce strict access controls and least privilege principles to minimize the potential impact of local attackers. 8. Monitor logs and system behavior for signs of exploitation attempts or unusual file system modifications. 9. For organizations with macOS fleet management, use Mobile Device Management (MDM) solutions to enforce patch compliance and application control policies. 10. Stay informed about any emerging exploits or additional patches related to this vulnerability.

Description

A permissions issue was addressed by removing the vulnerable code. This issue is fixed in macOS Sequoia 15.7, macOS Sonoma 14.8, macOS Tahoe 26. An app may be able to modify protected parts of the file system.

Impact

The primary impact of CVE-2025-43291 is on the integrity of macOS systems. An attacker who successfully exploits this vulnerability can modify protected parts of the file system, potentially leading to unauthorized changes in system files or configurations. This can facilitate persistence of malware, tampering with security controls, or disruption of normal system operations. Although confidentiality and availability are not directly impacted, the integrity compromise can indirectly lead to broader security issues, including privilege escalation or bypassing security mechanisms. For organizations worldwide, this vulnerability poses a risk to endpoint security, especially in environments with sensitive data or critical infrastructure relying on macOS devices. Attackers could leverage this flaw to implant backdoors or manipulate system behavior, complicating incident response and forensic investigations. The requirement for local access and user interaction limits remote exploitation but does not eliminate risk, particularly in scenarios involving social engineering or insider threats. Failure to patch could result in targeted attacks against enterprises, developers, or high-value macOS users.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (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, 01:53 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats