A memory corruption issue was addressed with improved state management.

published 2019-03-05 7y ago modified 2026-06-17 4mo ago also EUVD-2019-15778

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits: 0; none known

A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 12.1.3, macOS Mojave 10.14.3. Processing maliciously crafted web content may lead to arbitrary code execution.

Patch / fix

fixed in 2

Apple iOS iOS 12.1.3
Apple macOS macOS Mojave 10.14.3

Is CVE-2019-6211 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Apple iOS
Apple macOS

Classification

Weakness

CWE-787 Out-of-bounds Write

References

support.apple.com /HT209446
vendor-advisory
support.apple.com /HT209443
vendor-advisory

Sources

CVE List CVE-2019-6211
NVD CVE-2019-6211

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.