CVE-2025-43510
Apple Multiple Products Improper Locking Vulnerability
Apple Multiple Products
A memory corruption issue was addressed with improved lock state checking. This issue is fixed in iOS 18.7.2 and iPadOS 18.7.2, iOS 26.1 and iPadOS 26.1, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1. A malicious application may cause unexpected changes in memory shared between processes.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 20 March 2026. US federal agencies were required to remediate it by 3 April 2026.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 0.4%, which is higher than 29.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2025-43510 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-43510.
What does CVE-2025-43510 affect?
CVE-2025-43510 affects Apple Multiple Products. A memory corruption issue was addressed with improved lock state checking. This issue is fixed in iOS 18.7.2 and iPadOS 18.7.2, iOS 26.1 and iPadOS 26.1, macOS Sequoia 15.7.2, macOS Sonoma 14.8.2, macOS Tahoe 26.1, tvOS 26.1, visionOS 26.1, watchOS 26.1. A malicious application may cause unexpected changes in memory shared between processes.
How severe is CVE-2025-43510?
CVE-2025-43510 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 0.4%, higher than 29.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 3 April 2026.
How should organisations respond to CVE-2025-43510?
Apply the vendor patch for Apple Multiple Products as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.