Threats / Apple / CVE-2025-43529
CVE-2025-43529
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple Multiple Products vulnerability
Apple products contain a use-after-free vulnerability in WebKit that may lead to memory corruption when processing maliciously crafted web content.
Verdict
Today item — known-exploited.
A use-after-free flaw in WebKit affects multiple Apple platforms and products relying on WebKit for HTML processing. Exploitation requires user interaction with malicious web content and could result in memory corruption with potential code execution impact.
CISA KEV Yes · 2025-12-154EPSS 0.08585 (verify live)5Exploit Public PoC6CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-15).
Probability (EPSS)
EPSS 0.08585 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious web content designed to trigger improper memory handling in WebKit's HTML parser.
Business
Users of Apple Safari and other WebKit-based browsers face exposure to memory corruption attacks through routine web browsing.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I host or distribute the malicious content through compromised websites or watering hole attacks to reach target users.
Business
Apple's reputation and user trust are at risk if widespread exploitation occurs across iOS, iPadOS, and macOS ecosystems.
3
Lateral reach — past segmentation narrative 3
Attacker
I exploit the memory corruption to achieve code execution within the browser sandbox or application context.
Business
Device compromise and data exfiltration become possible, creating liability and support costs for affected users and enterprises.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05