Apple Multiple Products WebKit Use-After-Free Vulnerability (CVE-2023-32373)

Apple iOS, iPadOS, macOS, tvOS, watchOS, and Safari WebKit contain a use-after-free vulnerability that leads to code execution when processing maliciously crafted web content. This vulnerability could impact HTML parsers that use WebKit, including but not limited to Apple Safari and non-Apple products which rely on WebKit for HTML processing.

Published Jun 23, 2023 · Updated May 17, 2026

Why patchRisk explained in plain English

Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2023-06-12 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Use After Free (CWE-416) vulnerability in Apple Multiple Products. A use-after-free issue was addressed with improved memory management. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.6 and iPadOS 15.7.6, Safari 16.5, iOS 16.5 and iPadOS 16.5. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited. Exploitation requires remote network access, low attack complexity, no authentication required, and user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Apple Device Administrators

●Endpoint Security

●IT Security

●Running safari: v < 16.5; ipados: v < 15.7.6, 16.0 ≤ v < 16.5; iphone os: 15.0 ≤ v < 15.7.6, 16.0 ≤ v < 16.5; macos: v < 13.4; tvos: v < 16.5; watchos: v < 9.5; enterprise linux: 6.0, 7.0, 8.0, 9.0; webkitgtk\+: v < 2.42.3

Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2023-05-22 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2023-06-12.

How to patch

Manual remediation steps

Identify affected hosts: query inventory for general installs in scope.

Apply the vendor security update referenced in CVE-2023-32373's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.

Verify the fix per the vendor's published verification steps.

Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.

PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2023-32373 ↗ MSRC Advisory ↗ NVD ↗ Vendor Advisory