CVE-2019-7286 — Apple Multiple Products Memory Corruption Vulnerability

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jun 13, 2022 — passed 1585 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Apple iOS, Apple Iphone Os, Apple Mac Os X…).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
5. EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
6. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 15.94%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
• Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
• Hunt retroactively in logs from before May 23, 2022 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · apple/ios, apple/macos
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Affected products added · apple/iphone os, apple/mac os x
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 7.8
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• 2022
• Added to CISA KEV catalog
  May 22, 2022 · CISA
• 2019
• CVE published
  Dec 18, 2019 · apple

Source activity

Repeated readings are counted rather than listed.

• 1× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

• support.apple.com/HT209521
  Vendor Advisory, x_refsource_MISC, NIST National Vulnerability Database
• support.apple.com/HT209520
  Vendor Advisory, x_refsource_MISC, NIST National Vulnerability Database
• support.apple.com/HT209602
  Vendor Advisory, x_refsource_MISC, NIST National Vulnerability Database
• support.apple.com/HT209601
  Vendor Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-86950 Apple Multiple Products Out-of-Bounds Write Vulnerability KEV 17d
• Critical CVE-2026-65400 Apple macOS Improper Authentication Vulnerability KEV Aug 6, 2026
• Medium CVE-2026-43726 Use After Free in Apple Safari Jun 29, 2026
• Medium CVE-2026-43745 Out-of-bounds Write in Apple Safari Jun 29, 2026
• Medium CVE-2026-43742 Use After Free in Apple Safari Jun 29, 2026
• Medium CVE-2026-43743 Race Condition in Apple Ipados Jun 29, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-7286 is "Apple Multiple Products Memory Corruption Vulnerability", rated High. It affects iOS (Apple); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 15.94% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.