Skip to content
vulnerability

CVE-2025-43529

8.8
High
KEV · Exploited in wildEPSS 26%Patch available

A use-after-free issue was addressed with improved memory management. This issue is fixed in Safari 26.2, iOS 18.7.3 and iPadOS 18.7.3, iOS 26.2 and iPadOS 26.2, macOS Tahoe 26.2, tvOS 26.2, visionOS 26.2, watchOS 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.

exploited
Yes, in CISA KEV since 15 Dec 2025fix by 5 Jan 2026 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 25.7%
Published 17 Dec 2025Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: noAV · networkCWE-416· Use After Free

Can a WAF block it? No. This is a use-after-free memory bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
common questions

Is CVE-2025-43529 being exploited?

Yes. CVE-2025-43529 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-43529?

CVE-2025-43529 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-43529?

Yes. A fix has been recorded for CVE-2025-43529. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-43529 affect?

CVE-2025-43529 affects apple:safari, apple:ipados, apple:iphone_os, apple:macos, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
apple:safariapple:ipadosapple:iphone_osapple:macosapple:tvosapple:visionosapple:watchos
affected versions
Apple iOS and iPadOS
  • affected< 18.7.3
  • affected< 26.2
Apple macOS
  • affected< 26.2
Apple Safari
  • affected< 26.2
Apple tvOS
  • affected< 26.2
Apple visionOS
  • affected< 26.2
Apple watchOS
  • affected< 26.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 7 GitHub proofs of concept

GitHub proofs of concept
+3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 18 Dec 2025 (SSVC 2.0.3).

timeline

  1. 15 Dec 2025Added to CISA KEV (exploited in the wild)
  2. 17 Dec 2025Published · 3 days later
  3. 18 Dec 2025CISA SSVC assessment: exploitation active · same day later
  4. 5 Jan 2026First proof-of-concept repository on GitHub (unvetted) · 18 days later
  5. 5 Jan 2026CISA remediation due date (US federal agencies) · same day later
  6. 21 Sept 2026CVE record last updated · 260 days (about 9 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 42 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
8 references in the CVE record: 8 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved