basicsecurity.net
Proof, not just disclosure.
Threats / Apple / CVE-2023-32435
CVE-2023-32435 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Apple Multiple Products vulnerability

Apple WebKit memory corruption vulnerability in iOS, iPadOS, macOS, and Safari enables remote code execution through malicious web content processing.

Verdict

Today item — known-exploited.

Out-of-bounds write flaw in WebKit HTML parsing allows unauthenticated attackers to achieve arbitrary code execution on affected Apple devices and third-party products using WebKit, with confirmed active exploitation.

CISA KEV Yes · 2023-06-233EPSS 0.23052 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
13 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-06-23).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.23052 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
Craft malicious HTML or web content designed to trigger out-of-bounds memory write in WebKit parser
Business
User device compromised through routine web browsing without user interaction beyond visiting attacker-controlled or compromised site
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Deliver payload via web page, email link, or embedded content to trigger memory corruption during parsing
Business
Attacker gains code execution context with privileges of Safari or affected application process
3

Lateral reach — past segmentation narrative 3

Attacker
Execute arbitrary code post-exploitation to establish persistence or exfiltrate sensitive data
Business
Confidentiality and integrity of user data at risk across iOS, iPadOS, and macOS ecosystems
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 13 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by apple (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by appleCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.