Skip to content

CVE-2023-32409

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.

CVSS
8.6Highscored by CISA
Exploited in the wild
Yes, in CISA KEV since 22 May 2023CISA deadline for US federal agencies: 12 Jun 2023
EPSS
16.5%chance of exploitation in the next 30 daystop 3% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
23 Jun 2023analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable
At runtime
Attack vector
network
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Apple iOS and iPadOS< 15.7< 16.5Vendor says fixed in: not stated
Apple macOS< 13.4Vendor says fixed in: not stated
Apple Safari< 16.5Vendor says fixed in: not stated
Apple tvOS< 16.5Vendor says fixed in: not stated
Apple watchOS< 9.5Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • apple:safari
  • apple:ipados
  • apple:iphone_os
  • apple:macos
  • apple:tvos
  • apple:watchos

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 22 May 2023.
CISA due date
12 Jun 2023, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation active, automatable yes, technical impact partialAssessed by CISA 27 Jan 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 22 May 2023Added to CISA KEV (exploited in the wild)
  2. 12 Jun 2023CISA remediation due date (US federal agencies)21 days later
  3. 23 Jun 2023Published12 days later
  4. 27 Jan 2025CISA SSVC assessment: exploitation active584 days (about 2 years) later
  5. 12 Jan 2026CVE record last updated350 days (about 12 months) later
  6. 12 Nov 2026Analysed by vulneraibility.com304 days (about 10 months) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeChangedImpact crosses a security boundary into other components.
ConfidentialityNoneNo data disclosure.
IntegrityHighComplete modification possible.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2023-32409 being exploited?

Yes. CVE-2023-32409 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-32409?

CVE-2023-32409 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-32409?

Yes. A fix has been recorded for CVE-2023-32409. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-32409 affect?

CVE-2023-32409 affects apple:safari, apple:ipados, apple:iphone_os, apple:macos, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

7 references in the CVE record, grouped by the tags the record gives them.

Other links (7)

Show 1 more
  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-32409

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com