Threats / Apple / CVE-2019-7287
CVE-2019-7287
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Apple iOS vulnerability
Apple iOS memory corruption vulnerability enabling remote code execution. Exploited in the wild.
Verdict
Today item — known-exploited.
Out-of-bounds write in iOS allows unauthenticated remote attackers to execute arbitrary code without user interaction, posing critical risk to device integrity and data confidentiality.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 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-05-23).
Probability (EPSS)
EPSS 0.04589 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, iOS. Confirm exact fixed builds in the vendor advisory.
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.
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 input that triggers an out-of-bounds write in iOS memory handling.
Business
Attackers gain arbitrary code execution capability on millions of iOS devices globally.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I deliver the exploit remotely through network communication or media processing without requiring user action.
Business
Attack surface spans all iOS users regardless of awareness or defensive posture.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access or exfiltrate sensitive data from the compromised device.
Business
Customer privacy breaches, credential theft, and loss of trust in Apple ecosystem security.
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