Threats / Apple / CVE-2019-8605
CVE-2019-8605
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Apple Multiple Products vulnerability
Use-after-free vulnerability in Apple operating systems allows malicious applications to execute code with system privileges.
Verdict
Today item — known-exploited.
A use-after-free flaw in iOS, macOS, tvOS, and watchOS enables privilege escalation through malicious application execution. Active exploitation in the wild confirms practical threat; however, attack requires local application installation.
CISA KEV Yes · 2022-06-274EPSS 0.17438 (verify live)5Exploit Public PoC6CVSS 7.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
2 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 2022-06-27).
Probability (EPSS)
EPSS 0.17438 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) · Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 922 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious application that exploits the use-after-free condition in the operating system kernel.
Business
User device security is compromised when a seemingly legitimate app is installed from app stores or third-party sources.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger the memory corruption by performing specific operations that cause the freed memory to be reallocated and accessed.
Business
System integrity fails as the vulnerability allows arbitrary code execution at the highest privilege level.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with system privileges, gaining complete control over the device and all user data.
Business
Confidentiality, integrity, and availability of all device data and services are lost; user trust in the platform erodes.
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