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

Apple Multiple Products vulnerability

Apple's iOS, iPadOS, macOS, tvOS, and watchOS contain an unspecified vulnerability allowing a malicious app to modify sensitive kernel state, potentially enabling privilege escalation or system compromise.

Verdict

Today item — known-exploited.

An installed application can exploit this vulnerability to alter kernel-level state without authorization. Active exploitation in the wild indicates practical weaponization. The lack of user interaction requirements and broad platform impact create significant risk across Apple's ecosystem.

CISA KEV Yes · 2023-07-263EPSS 0.01002 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
19 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-07-26).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01002 — 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
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
I distribute a seemingly benign app through official or third-party app stores to establish initial presence on target devices.
Business
User trust in app distribution channels is undermined; legitimate-appearing applications become vectors for system compromise.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I trigger the kernel state modification vulnerability from within my app's sandboxed execution context to escalate privileges.
Business
The device's security boundary is breached; kernel-level access enables complete system control and data exfiltration.
3

Lateral reach — past segmentation narrative 3

Attacker
I persist malicious code at the kernel level, evading app removal and standard security controls.
Business
Remediation becomes difficult; affected devices remain compromised even after app deletion, requiring OS-level intervention.
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)
  • 19 reported-exploitation source(s)
  • 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.