Skip to content
Web

CVE-2023-43010

8.8
High
EPSS 0.89%Patch availableMar 12, 2026

Web content processing may crash Safari/WebKit via memory corruption.

common questions

Is CVE-2023-43010 being exploited?

Not confirmed. CVE-2023-43010 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.89% probability of exploitation in the next 30 days.

How severe is CVE-2023-43010?

CVE-2023-43010 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-2023-43010?

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

What does CVE-2023-43010 affect?

CVE-2023-43010 affects iOS 15.x (before 15.8.7), iOS 16.x (before 16.7.15), iPadOS 15.x (before 15.8.7), iPadOS 16.x (before 16.7.15), and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2023-43010?

Update to Apple OS/browser versions listed (Safari 17.2, iOS 17.2, macOS 14.2).

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

executive summary
technical analysis
affected
iOS 15.x (before 15.8.7)iOS 16.x (before 16.7.15)iPadOS 15.x (before 15.8.7)iPadOS 16.x (before 16.7.15)macOS prior to 14.2 (Sonoma)Safari prior to 17.2
impact

Remote DoS: crafted web content can trigger memory corruption and crash the process.

action required

Patch when possible

affected versions
Apple iOS and iPadOS
  • affected< 17.2
  • affected< 16.7.15
  • affected< 15.8.7
Apple macOS
  • affected< 14.2
Apple Safari
  • affected< 17.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.

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
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free