IDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSEIDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSE
Impactr Logoimpactr
FeaturesHow it worksEvidencePricingLearnVulnerability DBCompare
  1. Home
  2. Vulnerability Database
  3. CVE-2025-43510
CVE-2025-43510 CISA KEV — actively exploited

Apple Multiple Products Improper Locking Vulnerability

Apple — iOS and iPadOS

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 scoreHigh

7.8

EPSS — exploitation probabilityLow

0.4%

Vector breakdown

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

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

Published
Dec 12, 2025
Modified
Apr 2, 2026
Added to KEV
Mar 20, 2026
Federal patch due
Apr 3, 2026

CISA 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.

Weakness classification

CWE-667Improper Locking

Proof-of-concept & exploitation references

Weaponization

Nuclei template

Not found

Metasploit module

Not found

Public repositories whose name or description references CVE-2025-43510, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.

No public GitHub repositories referencing CVE-2025-43510 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.

References

  • support.apple.com
  • support.apple.com
  • support.apple.com
  • support.apple.com
  • support.apple.com
  • support.apple.com
  • support.apple.com
  • support.apple.com

Frequently asked questions

What is CVE-2025-43510?

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 has a CVSS base score of 7.8 out of 10 (CVSS 3.1).

Is CVE-2025-43510 actively exploited in the wild?

Yes. CVE-2025-43510 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Mar 20, 2026, meaning CISA has confirmed evidence of active exploitation.

What is the EPSS score for CVE-2025-43510?

0.4% - meaning FIRST.org's EPSS model estimates a 0.4% probability this vulnerability will be exploited in the wild within 30 days (28% percentile among all scored CVEs).

What type of vulnerability is CVE-2025-43510?

CVE-2025-43510 is classified under CWE-667 (CWE-667 Improper Locking).

Cross-checked against

  • NVD (NIST)
  • MITRE CVE Record
  • CISA KEV
  • FIRST.org EPSS
  • GitHub Advisory Database
  • GitHub public repository search

Impactr finds and proves whether CVE-2025-43510 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.

Join the waitlist
← Vulnerability database
Impactr Logoimpactr

Built by hackers, for the code you ship. Autonomous AI penetration testing for modern web apps and APIs.

© 2026 Impactr

Product

FeaturesCoverageUse casesEvidencePricingWaitlist

Resources

VulnerabilitiesVulnerability databaseGuidesComparisonsGlossaryCWE databaseBy industryBy languageHTTP status codesSecurity headers

Company

ContactTwitterLinkedInGitHub