dbcve.org
SafariWeb browser · Apple

CVE-2023-43010

HIGH · 8.8 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 14.2 / 15.8.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The issue was addressed with improved memory handling. This issue is fixed in iOS 17.2 and iPadOS 17.2, macOS Sonoma 14.2, Safari 17.2, iOS 16.7.15 and iPadOS 16.7.15, iOS 15.8.7 and iPadOS 15.8.7. Processing maliciously crafted web content may lead to memory corruption.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Memory corruption vulnerability in WebKit affecting Safari, iOS, and iPadOS. Processing maliciously crafted web content can lead to arbitrary code execution due to improper memory handling during rendering.

MitigationApply vendor-supplied patches: update to iOS 17.2+/iPadOS 17.2+/macOS Sonoma 14.2+/Safari 17.2+ or the legacy patches (16.7.15/15.8.7) for older supported versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SafariWeb browser
Affected:< 17.2
IpadosOperating system
Affected:< 15.8.7>= 16.0, < 16.7.15>= 17.0, < 17.2
Iphone OsOperating system
Affected:< 15.8.7>= 16.0, < 16.7.15>= 17.0, < 17.2
macOSOperating system
Affected:< 14.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari, or run `defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString` in Terminal
    Affected if Version is less than 17.2
  2. Check macOS version
    Click Apple menu > About This Mac, or run `sw_vers -productVersion` in Terminal
    Affected if Version is less than 14.2 (this includes all Safari and WebKit instances bundled with older macOS)
  3. Check iOS version on iPhone
    Go to Settings > General > About, or connect device to computer and run `idevicesysversion` (if tools available)
    Affected if Version is less than 15.8.7, or between 16.0 and 16.7.14, or between 17.0 and 17.1.x (Safari on iOS is tied to OS version)
  4. Check iPadOS version on iPad
    Go to Settings > General > About, or connect device to computer and run `idevicesysversion` (if tools available)
    Affected if Version is less than 15.8.7, or between 16.0 and 16.7.14, or between 17.0 and 17.1.x (Safari and WebKit on iPadOS are tied to OS version)

If Safari is below 17.2 on macOS, or macOS is below 14.2, or iOS/iPadOS falls into any of the vulnerable version ranges, the environment is affected by this WebKit memory corruption flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.2 / 15.8.7 / 16.7.15 or later
Fixed in 14.215.8.716.7.15
Interim mitigation

Apply vendor-supplied patches: update to iOS 17.2+/iPadOS 17.2+/macOS Sonoma 14.2+/Safari 17.2+ or the legacy patches (16.7.15/15.8.7) for older supported versions.

Recommended fix High confidence

Safari 17.2; macOS Sonoma 14.2; iOS 17.2; iPadOS 17.2; iOS 16.7.15; iPadOS 16.7.15; iOS 15.8.7; iPadOS 15.8.7

  1. Identify the affected Apple device and current OS version (Safari, iOS, iPadOS, or macOS)
  2. For Safari on any platform: upgrade to Safari 17.2 or later
  3. For iPhone: upgrade to iOS 15.8.7, iOS 16.7.15, or iOS 17.2 (or later)
  4. For iPad: upgrade to iPadOS 15.8.7, iPadOS 16.7.15, or iPadOS 17.2 (or later)
  5. For macOS: upgrade to macOS Sonoma 14.2 or later
  6. After upgrade, verify the Safari version matches the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-43010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-43010 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data