CVE-2025-43510
KEVApple Multiple Products Improper Locking Vulnerability
Description
Apple watchOS, iOS, iPadOS, macOS, visionOS, and tvOS contain an improper locking vulnerability that could allow a malicious application to cause unexpected changes in memory shared between processes.
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.
CVSS 3.1 vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HPublishedDec 12, 2025
Last modifiedOct 7, 2026
Added to KEVMar 20, 2026
Remediation dueApr 3, 2026
References
- support.apple.com/en-us/125632Release NotesVendor Advisory
- support.apple.com/en-us/125633Release NotesVendor Advisory
- support.apple.com/en-us/125634Release NotesVendor Advisory
- support.apple.com/en-us/125635Release NotesVendor Advisory
- support.apple.com/en-us/125636Release NotesVendor Advisory
- support.apple.com/en-us/125637Release NotesVendor Advisory
- support.apple.com/en-us/125638Release NotesVendor Advisory
- support.apple.com/en-us/125639Release NotesVendor Advisory
- cloud.google.com/blog/topics/threat-intelligence/darksword-ios-exploit-chain/Technical Description
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-43510US Government Resource
0 recent articles mention this CVE
69
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 208 days
- CVSS
- 7.8 HIGH
- EPSS (30-day exploit probability)
- 0.36% · top 71% of all CVEs
- Weakness
- CWE-667
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.