Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2023-32409: Web Content sandbox escape in Apple WebKit

Published Jun 23, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.6High · v3.1
EPSS16.5%97th percentile
CISA KEVYesAdded May 22, 2023
In the wildActivePer CISA KEV
Vendor
Apple
IdentifiersCVE-2023-32409CWE-119
Also known asironloader

CVE-2023-32409 is a bounds-checking vulnerability in Apple WebKit that may allow a remote attacker to escape the Web Content sandbox. Apple corrected the issue with improved bounds checks and acknowledged a report of possible active exploitation. The vulnerability has been used in spyware exploitation chains and is associated with the IronLoader sandbox-escape component of the Coruna iOS exploit kit. The specific vulnerable function and precise memory-corruption mechanism have not been established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can bypass Web Content process isolation, allowing attacker activity outside the browser content sandbox. The vulnerability has been used alongside other exploits to deploy spyware. Kernel privilege escalation and sensitive-data theft associated with complete exploit chains should not be attributed to this vulnerability alone.

Mitigation

If you can’t patch tonight, do this now.

On supported iPhones, enable Lockdown Mode to block observed Coruna attack chains when immediate updating is not possible. Coruna also avoids private browsing sessions, and Safari Safe Browsing helps block known malicious delivery sites. These measures address observed exploit delivery and are not substitutes for installing the vulnerability fix.

Remediation

Patch, then assume compromise.

Install the latest supported Apple security updates. CVE-specific fixed releases include Safari 16.5, macOS Ventura 13.4, iOS and iPadOS 16.5, and iOS and iPadOS 15.7.8. The listed watchOS and tvOS fix versions differ: watchOS 9.5 and tvOS 16.5 are identified as fixed releases, while later reporting identifies backported patches in watchOS 9.6 and tvOS 16.6. Use the latest supported releases and verify coverage in Apple's product-specific security bulletins. Broader advisory recommendations for iOS and iPadOS 15.7.6 do not establish that those versions fix this particular vulnerability.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
webkit-cve-2024-23222This repository is a multi-file Apple WebKit/JSC exploit research collection centered on CVE-2024-23222, with numerous auxiliary HTML PoCs for other Safari/WebKit vulnerabilities. It is not a framework module; it is a standalone research repo containing browser-delivered exploit pages, a local Python HTTP collector, and one native C helper. Structure: - README.md documents the intended full exploit chain: a malicious HTML page triggers CVE-2024-23222 in JavaScriptCore, obtains addrof/read64/write64 primitives, then uses a crafted WebAssembly indirect-call trampoline to invoke native libc functions on an A11 iPhone X running iOS 16.4.1. The documented post-exploitation action is opening and writing /tmp/pwned_cve_2024_23222, presented as proof of sandbox escape. - poc/server.py is the operator-side infrastructure. It serves HTML files over HTTP on port 8765, exposes GET/POST /results for telemetry collection, and GET/POST /signal for auxiliary signaling. - find_gigacage.c is a native Mach-based memory scanner that uses task_for_pid, vm_region_recurse_64, and vm_read to locate JSC/Gigacage-related regions and sentinels in another process. This supports exploit development and address discovery rather than remote exploitation. - poc/exploit_23222.html is an earlier standalone Stage 1 exploit for CVE-2024-23222. It contains the core exploitation logic: WebAssembly modules, type confusion setup, arbitrary read/write primitives, addrof, and JIT/JSC structure offset handling. It posts progress markers and results back to /results. - poc/ironloader_diag.html is a diagnostic page for CVE-2023-32409 (“IronLoader”), reusing similar Stage 1 primitives and adding logic to inspect IPC/GPU-related structures. - The remaining poc/cve-*.html files are mostly self-contained browser PoCs or vulnerability checkers for specific CVEs. They generally trigger a suspicious code path, observe crashes/misbehavior, and POST a verdict plus logs to /results. Several are more detection-oriented than weaponized. Main exploit capabilities: - Browser-based initial access via a malicious HTML page. - JSC/WebAssembly memory corruption leading to arbitrary address disclosure and 64-bit read/write in the renderer. - Arbitrary native function invocation by overwriting a WASM indirect-call target slot. - Demonstrated sandbox escape behavior by calling _open/_write on /tmp/pwned_cve_2024_23222. - Extensive telemetry/logging back to a local HTTP server. Notable targeting details: - Primary target is Apple iPhone X (A11, no PAC), iOS 16.4.1, Safari 16.4.1. - The exploit assumes device/version-specific offsets and an ASLR slide known in advance/offline. - README explicitly notes limitations such as inability to directly read dyld cache from JS and failure of mmap(PROT_EXEC), indicating this is a real exploit-development repo rather than a simple detector. Assessment: - The repository contains genuine exploit code and PoCs. The main CVE-2024-23222 chain is operational but environment-specific, with a basic hardcoded payload (proof-file creation) rather than a flexible post-exploitation framework. Auxiliary files broaden the repo into a WebKit vulnerability lab with multiple browser-based tests and diagnostics.Umit-MHL · Disclosed May 19, 2026 · markdown · c · browser · web · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
AppleSafariapplication
AppleTvosoperating_system
AppleWatchosoperating_system
FAQ

Frequently asked questions

Is CVE-2023-32409 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 22, 2023.
Is there a public exploit for CVE-2023-32409?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2023-32409, the earliest disclosed May 19, 2026.
Is there a patch for CVE-2023-32409?
Install the latest supported Apple security updates. CVE-specific fixed releases include Safari 16.5, macOS Ventura 13.4, iOS and iPadOS 16.5, and iOS and iPadOS 15.7.8.
What products are affected by CVE-2023-32409?
Apple Ipados, Apple Iphone Os, Apple Macos, Apple Safari, Apple Tvos, and 1 more.
How severe is CVE-2023-32409?
CVE-2023-32409 has a CVSS v3.1 score of 8.6 (High) and an EPSS score of 16.5% (97th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence16Every report linking this CVE to a named adversary.
Associated malware24Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.