Class familyApple · Multiple Products
Apple iOS and macOS memory corruption flaws, 2016–2026
67 Multiple Products CVEs with CWE-119 weaknesses, 25 Aug 2016 to 17 Aug 2026. 7 are in CISA KEVThe US Cybersecurity and Infrastructure Security Agency’s list of Known Exploited Vulnerabilities. A CVE is added when CISA has evidence that attackers are using it..
CVEs by year
Published each year. Select a CVE to open it.Grouped by product and weakness type (CWE); not proven to share a root cause.
1 2016’16
2017’17
2018’18
1 2019’19
2020’20
2 2021’21
1 2022’22
2023’23
3 2024’24
25 2025’25
34 2026’26
In CISA KEVNot in KEV
20161 CVE, 1 in KEV
20191 CVE, 1 in KEV
20212 CVEs, 2 in KEV
20221 CVE
20243 CVEs
202525 CVEs, 2 in KEV
- CVE-2024-54551
- CVE-2025-24216
- CVE-2025-31200
- CVE-2025-31204
- CVE-2025-31223
- CVE-2025-31238
- CVE-2025-31257
- CVE-2025-24189
- CVE-2025-31273
- CVE-2025-31278
- CVE-2025-43212
- CVE-2025-43213
- CVE-2025-43214
- CVE-2025-43277
- CVE-2025-31277
- CVE-2025-43272
- CVE-2025-43343
- CVE-2025-43419
- CVE-2025-43425
- CVE-2025-43429
- CVE-2025-43431
- CVE-2025-43433
- CVE-2025-43435
- CVE-2025-43441
- CVE-2025-43539
202634 CVEs, 1 in KEV
- CVE-2025-46298
- CVE-2026-20635
- CVE-2026-20636
- CVE-2026-20644
- CVE-2026-20700
- CVE-2026-28847
- CVE-2026-28901
- CVE-2026-28902
- CVE-2026-28903
- CVE-2026-28904
- CVE-2026-28905
- CVE-2026-28913
- CVE-2026-28940
- CVE-2026-28944
- CVE-2026-28953
- CVE-2026-28955
- CVE-2026-28990
- CVE-2026-43658
- CVE-2026-39872
- CVE-2026-43663
- CVE-2026-43707
- CVE-2026-43740
- CVE-2026-43673
- CVE-2026-43711
- CVE-2026-43729
- CVE-2026-64716
- CVE-2026-64757
- CVE-2026-28984
- CVE-2026-43794
- CVE-2026-43795
- CVE-2026-64788
- CVE-2026-65334
- CVE-2026-65338
- CVE-2026-65341
CVEs in this family
Table view of the years above| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2016-4657KEV | 25 Aug 2016 | Apple iOS Webkit Memory Corruption Vulnerability | Grouped by weakness | 79.0 |
| CVE-2018-4344KEV | 3 Apr 2019 | Apple Multiple Products Memory Corruption Vulnerability | Grouped by weakness | 60.2 |
| CVE-2021-30983KEV | 24 Aug 2021 | Apple iOS and iPadOS Buffer Overflow Vulnerability | Grouped by weakness | 60.9 |
| CVE-2021-30666KEV | 8 Sep 2021 | Apple iOS WebKit Buffer Overflow Vulnerability | Grouped by weakness | 61.6 |
| CVE-2022-32939 | 1 Nov 2022 | The issue was addressed with improved bounds checks | Grouped by weakness | 9.9 |
| CVE-2024-23213 | 23 Jan 2024 | The issue was addressed with improved memory handling | Grouped by weakness | 21.0 |
| CVE-2024-27820 | 10 Jun 2024 | The issue was addressed with improved memory handling | Grouped by weakness | 17.9 |
| CVE-2024-27851 | 10 Jun 2024 | The issue was addressed with improved bounds checks | Grouped by weakness | 16.7 |
| CVE-2024-54551 | 20 Mar 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 15.4 |
| CVE-2025-24216 | 31 Mar 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 14.4 |
| CVE-2025-31200KEV | 16 Apr 2025 | Apple Multiple Products Memory Corruption Vulnerability | Grouped by weakness | 69.4 |
| CVE-2025-31204 | 12 May 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 16.6 |
| CVE-2025-31223 | 12 May 2025 | The issue was addressed with improved checks | Grouped by weakness | 15.2 |
| CVE-2025-31238 | 12 May 2025 | The issue was addressed with improved checks | Grouped by weakness | 17.7 |
| CVE-2025-31257 | 12 May 2025 | This issue was addressed with improved memory handling | Grouped by weakness | 16.5 |
| CVE-2025-24189 | 19 May 2025 | The issue was addressed with improved checks | Grouped by weakness | 17.1 |
| CVE-2025-31273 | 29 Jul 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 19.5 |
| CVE-2025-31278 | 29 Jul 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 20.0 |
| CVE-2025-43212 | 29 Jul 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 17.4 |
| CVE-2025-43213 | 29 Jul 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 15.7 |
| CVE-2025-43214 | 29 Jul 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 17.6 |
| CVE-2025-43277 | 29 Jul 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 10.1 |
| CVE-2025-31277KEV | 30 Jul 2025 | Apple Multiple Products Buffer Overflow Vulnerability | Grouped by weakness | 69.5 |
| CVE-2025-43272 | 15 Sep 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 17.6 |
| CVE-2025-43343 | 15 Sep 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 18.2 |
| CVE-2025-43419 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 13.1 |
| CVE-2025-43425 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 13.7 |
| CVE-2025-43429 | 4 Nov 2025 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 17.7 |
| CVE-2025-43431 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 17.8 |
| CVE-2025-43433 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 19.6 |
| CVE-2025-43435 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 14.0 |
| CVE-2025-43441 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 15.3 |
| CVE-2025-43539 | 12 Dec 2025 | The issue was addressed with improved bounds checks | Grouped by weakness | 24.9 |
| CVE-2025-46298 | 9 Jan 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 11.1 |
| CVE-2026-20635 | 11 Feb 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 8.8 |
| CVE-2026-20636 | 11 Feb 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.5 |
| CVE-2026-20644 | 11 Feb 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.4 |
| CVE-2026-20700KEV | 11 Feb 2026 | Apple Multiple Buffer Overflow Vulnerability | Grouped by weakness | 68.8 |
| CVE-2026-28847 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 15.9 |
| CVE-2026-28901 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 9.6 |
| CVE-2026-28902 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 11.2 |
| CVE-2026-28903 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 11.2 |
| CVE-2026-28904 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.3 |
| CVE-2026-28905 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.3 |
| CVE-2026-28913 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.4 |
| CVE-2026-28940 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 15.9 |
| CVE-2026-28944 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.0 |
| CVE-2026-28953 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.3 |
| CVE-2026-28955 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 16.7 |
| CVE-2026-28990 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 15.9 |
| CVE-2026-43658 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.2 |
| CVE-2026-39872 | 29 Jun 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.7 |
| CVE-2026-43663 | 29 Jun 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.7 |
| CVE-2026-43707 | 29 Jun 2026 | A memory corruption issue was addressed with improved memory handling | Grouped by weakness | 15.1 |
| CVE-2026-43740 | 29 Jun 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 11.4 |
| CVE-2026-43673 | 27 Jul 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 6.8 |
| CVE-2026-43711 | 27 Jul 2026 | A memory corruption issue was addressed with improved memory handling | Grouped by weakness | 6.8 |
| CVE-2026-43729 | 27 Jul 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 6.8 |
| CVE-2026-64716 | 27 Jul 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 6.8 |
| CVE-2026-64757 | 27 Jul 2026 | A memory corruption issue was addressed with improved state management | Grouped by weakness | 14.3 |
| CVE-2026-28984 | 17 Aug 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 5.4 |
| CVE-2026-43794 | 17 Aug 2026 | A memory corruption issue was addressed with improved memory handling | Grouped by weakness | 13.5 |
| CVE-2026-43795 | 17 Aug 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.6 |
| CVE-2026-64788 | 17 Aug 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 12.2 |
| CVE-2026-65334 | 17 Aug 2026 | A memory corruption issue was addressed with improved state management | Grouped by weakness | 10.9 |
| CVE-2026-65338 | 17 Aug 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.9 |
| CVE-2026-65341 | 17 Aug 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 6.9 |