CVE-2023-41974 — IPADOS
HIGHCVE-2023-41974 is a high-severity (CVSS 7.8) Use After Free vulnerability in apple ipados. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-03-05) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
A use-after-free issue was addressed with improved memory management. This issue is fixed in iOS 17 and iPadOS 17, iOS 15.8.7 and iPadOS 15.8.7. An app may be able to execute arbitrary…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-03-05. Federal agencies were required to remediate by 2026-03-26.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-41974.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2023-41974 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
A use-after-free issue was addressed with improved memory management. This issue is fixed in iOS 17 and iPadOS 17, iOS 15.8.7 and iPadOS 15.8.7. An app may be able to execute arbitrary code with kernel privileges.
Affected Products
ipadosappleiphone osappleDetection & mitigation playbook
Vendor / applianceDetect
Inventory every apple ipados deployment and check each version against the affected-products list above.
Fix
Apply the apple ipados security patch or hotfix for CVE-2023-41974 on the affected version, following the vendor advisory for your exact build.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2023-41974 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.