IRONSMITHINTEL
HIGHCVSS8.6
|
Actively Exploited
|CISA KEV|CVE-2023-32409|Auth: none — unauthenticated|Reboot: required|Manual only

Apple Multiple Products WebKit Sandbox Escape Vulnerability (CVE-2023-32409)

Apple iOS, iPadOS, macOS, tvOS, watchOS, and Safari WebKit contain an unspecified vulnerability that can allow a remote attacker to break out of the Web Content sandbox. 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 partial data exposure, arbitrary modification of data. Federal agencies are required to remediate by 2023-06-12 under CISA BOD 22-01.

How the attack worksNo clicks needed

This vulnerability affects Apple Multiple Products. The issue was addressed with improved bounds checks. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.8 and iPadOS 15.7.8, Safari 16.5, iOS 16.5 and iPadOS 16.5. A remote attacker may be able to break out of Web Content sandbox. 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 no 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: 15.0 ≤ v < 15.7.8, 16.0 ≤ v < 16.5; iphone os: 15.0 ≤ v < 15.7.8, 16.0 ≤ v < 16.5; macos: 13.0 ≤ v < 13.4; tvos: v < 16.5; watchos: v < 9.5
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

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2023-32409's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
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-32409↗ MSRC Advisory↗ NVD↗ Vendor Advisory