How severe is CVE-2023-32409?

CVE-2023-32409 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-32409?

Affected package information for CVE-2023-32409 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-32409?

No fixed release is recorded for CVE-2023-32409 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2023-32409 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2023-32409 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-32409 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2023-32409, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-32409?

CVE-2023-32409 has an EPSS (Exploit Prediction Scoring System) score of 16.5%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2023-32409 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-32409 (Apple Multiple Products WebKit Sandbox Escape Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-05-22. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-06-12. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2023-32409 published, and has it been updated?

CVE-2023-32409 was published on June 23, 2023 and was last updated on March 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2023-32409

HIGH

CVE-2023-32409 is a high-severity (CVSS 8.6) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-05-22) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published

Jun 23, 2023

Updated

Mar 15, 2026

Affected

6 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-05-22. Federal agencies were required to remediate by 2023-06-12.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-32409.

EPSS Exploitation Probability

via FIRST.org ↗

16.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2023-32409 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

6 products · 8 configurations

ipadosapple

≥ 16.0 && < 16.5

range

iphone osapple

≥ 16.0 && < 16.5

range

macosapple

≥ 13.0 && < 13.4

range

Application

safariapple

< 16.5

range

tvosapple

< 16.5

range

watchosapple

< 9.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The issue was addressed with improved bounds checks. This issue is fixed…

support.apple.comGoogle-sheetMay 2023

The issue was addressed with improved bounds checks. This issue is fixed…

cisa.govCISAMay 2023

The issue was addressed with improved bounds checks. This issue is fixed…

nvd.nist.govNVDJun 2023

The issue was addressed with improved bounds checks. This issue is fixed…

support.apple.comGoogle-sheetJul 2023

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2023-32409 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-32409 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2023-32409

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2023-32409 in your dependencies?