How severe is CVE-2025-43529?

CVE-2025-43529 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-43529?

Affected package information for CVE-2025-43529 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-43529?

No fixed version has been published for CVE-2025-43529 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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

Yes. There are 3 known exploit references for CVE-2025-43529, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2025-43529 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-43529 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-43529 (Apple Multiple Products Use-After-Free WebKit Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-12-15. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-01-05. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2025-43529 published, and has it been updated?

CVE-2025-43529 was published on December 17, 2025 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-12-15 — agencies required to remediate by 2026-01-05

CVE-2025-43529

HIGH

Published

Dec 17, 2025

Updated

Mar 23, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk38th percentile+0.01%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A use-after-free issue was addressed with improved memory management. This issue is fixed in watchOS 26.2, Safari 26.2, iOS 18.7.3 and iPadOS 18.7.3, iOS 26.2 and iPadOS 26.2, macOS Tahoe 26.2, visionOS 26.2, tvOS 26.2. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26. CVE-2025-14174 was also issued in response to this report.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

zeroxjf/WebKit-UAF-ANGLE-OOB-Analysis

Analysis of CVE-2025-43529 (WebKit UAF) + CVE-2025-14174 (ANGLE OOB) exp

⭐ 100🍴 21Jun 2026

jir4vv1t/CVE-2025-43529

exploit for cve-2025-43529

⭐ 79🍴 10May 2026

bjrjk/CVE-2025-43529

Root Cause Analysis for CVE-2025-43529, a UAF vulnerability due to incor

⭐ 17🍴 1Feb 2026

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-43529 in your stack?

O3 detects CVE-2025-43529 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works