CVE-2025-43510
BaseFortify
Publication date: 2025-12-12
Last updated on: 2026-04-03
Assigner: Apple Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apple | ipados | to 18.7.2 (exc) |
| apple | ipados | 26.0 |
| apple | iphone_os | to 18.7.2 (exc) |
| apple | iphone_os | 26.0 |
| apple | macos | From 14.0 (inc) to 14.8.2 (exc) |
| apple | macos | From 15.0 (inc) to 15.7.2 (exc) |
| apple | macos | 26.0 |
| apple | tvos | to 26.1 (exc) |
| apple | visionos | to 26.1 (exc) |
| apple | watchos | to 26.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory corruption issue caused by improper lock state checking. It allows a malicious application to cause unexpected changes in memory that is shared between processes, potentially leading to instability or unauthorized behavior.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing a malicious application to manipulate shared memory unexpectedly, which could lead to application crashes, data corruption, or potentially unauthorized access to sensitive information across processes.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Apple devices to the fixed versions: watchOS 26.1, iOS 18.7.2 and 26.1, iPadOS 18.7.2 and 26.1, macOS Tahoe 26.1, visionOS 26.1, tvOS 26.1, macOS Sonoma 14.8.2, and macOS Sequoia 15.7.2. Applying these updates will address the memory corruption issue.