Skip to content

CVE-2025-43510

A memory corruption issue was addressed with improved lock state checking.

High Known exploited
Severity
7.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.36%
Chance of exploitation in the next 30 days. Higher than 29.29% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Mar 20, 2026
Weakness
CWE-667 Improper Locking
Fix
None yet
No fixed version published
Exploited in the wild. Apple Multiple Products Improper Locking Vulnerability (Apple Multiple Products). Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Due for U.S. federal agencies by Apr 3, 2026.

Description

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 to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 7.8

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

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-667: Improper Locking

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How to prevent it
  • Implementation: Use industry standard APIs to implement locking mechanism.

References

Timeline

  1. Published
  2. Added to CISA's Known Exploited Vulnerabilities catalog
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-567q-5qvw-pf92
filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale break
Low Same weakness, CWE-667
GHSA-6hcq-hmm3-jj3c
Spring MVC and WebFlux has Server Sent Event stream corruption
Low Same weakness, CWE-667
GHSA-m2v9-w374-5hj9
vyper default functions don't respect nonreentrancy keys
Medium Same weakness, CWE-667
GHSA-3hg2-r75x-g69m
Vyper has incorrect re-entrancy lock when key is empty string
Medium Same weakness, CWE-667
GHSA-vr8j-hgmm-jh9r
Denial of service by double-checked locking in openssl-src
High Same weakness, CWE-667
GO-2022-0830
Denial of Service in Gitea
High Same weakness, CWE-667
GHSA-h67m-xg8f-fxcf
Deadlock in mutually recursive `tf.function` objects
Medium Same weakness, CWE-667
CVE-2021-1782
A race condition was addressed with improved locking.
High Known exploited Same weakness, CWE-667
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor