CVE-2025-31264VulnerabilityPublished 29 May 2025Updated 2 Apr 2026

CVE-2025-31264: Apple macOS · An attacker with physical access to a locked device may be able to view sensitive user information in

Affects Apple macOSSource CVE Database V5

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

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.6Medium

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

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

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

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: 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: 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 29 May 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 2026-10-26.

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

To mitigate CVE-2025-31264, organizations should: 1) Immediately apply the security updates provided by Apple for macOS Sequoia 15.4, Sonoma 14.7.5, and Ventura 13.7.5 or later versions to ensure the vulnerability is patched. 2) Enforce strict physical security controls to prevent unauthorized access to devices, including secure storage, access logging, and surveillance in sensitive areas. 3) Implement full disk encryption and strong lock screen policies with short timeout intervals to minimize exposure time. 4) Educate users on the importance of locking devices when unattended and reporting lost or stolen devices promptly. 5) Consider deploying endpoint detection and response (EDR) solutions that can detect suspicious local access attempts or unauthorized data access. 6) Regularly audit device access logs and monitor for unusual physical access patterns. 7) For high-risk environments, consider additional hardware-based protections such as secure enclave usage or biometric authentication enhancements. These measures collectively reduce the likelihood of successful exploitation and limit the potential damage from physical access attacks.

Description

An authentication issue was addressed with improved state management. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An attacker with physical access to a locked device may be able to view sensitive user information.

Impact

The primary impact of CVE-2025-31264 is the unauthorized disclosure of sensitive user information on locked macOS devices. This compromises confidentiality, potentially exposing personal data, credentials, or corporate information stored or accessible on the device. While the vulnerability does not affect system integrity or availability, the exposure of sensitive data can lead to further attacks such as identity theft, corporate espionage, or targeted social engineering. Organizations with macOS devices in environments where physical security is limited—such as shared offices, public areas, or during travel—face increased risk. The requirement for physical access limits remote exploitation, but insider threats or opportunistic attackers could leverage this vulnerability. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop tools to exploit this flaw. Failure to patch could result in data breaches and loss of user trust, with potential regulatory and compliance consequences for organizations handling sensitive information.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (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:31 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats