Class familyApple · iOS, iPadOS, and macOS
Apple iOS and macOS buffer overflow flaws, 2021–2026
64 iOS, iPadOS, and macOS CVEs with CWE-120 weaknesses, 24 Aug 2021 to 14 Sep 2026. 4 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 2021’21
1 2022’22
4 2023’23
9 2024’24
15 2025’25
34 2026’26
In CISA KEVNot in KEV
20211 CVE, 1 in KEV
20221 CVE
20234 CVEs, 1 in KEV
20249 CVEs
202515 CVEs, 2 in KEV
202634 CVEs
- CVE-2026-20608
- CVE-2026-20635
- CVE-2026-20636
- CVE-2026-20644
- CVE-2026-20652
- CVE-2023-43010
- CVE-2026-20664
- CVE-2026-28857
- CVE-2026-28858
- CVE-2026-28859
- CVE-2026-28875
- CVE-2026-28847
- CVE-2026-28901
- CVE-2026-28902
- CVE-2026-28903
- CVE-2026-28904
- CVE-2026-28905
- CVE-2026-28925
- CVE-2026-28953
- CVE-2026-28955
- CVE-2026-28959
- CVE-2026-39869
- CVE-2026-43658
- CVE-2026-43776
- CVE-2026-43807
- CVE-2026-64722
- CVE-2026-64747
- CVE-2026-64767
- CVE-2026-64705
- CVE-2026-65357
- CVE-2026-65398
- CVE-2026-84497
- CVE-2026-84609
- CVE-2026-84632
CVEs in this family
Table view of the years above| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2021-30983KEV | 24 Aug 2021 | Apple iOS and iPadOS Buffer Overflow Vulnerability | Grouped by weakness | 60.9 |
| CVE-2022-32941 | 1 Nov 2022 | The issue was addressed with improved bounds checks | Grouped by weakness | 22.9 |
| CVE-2023-23535 | 8 May 2023 | The issue was addressed with improved memory handling | Grouped by weakness | 6.9 |
| CVE-2023-27955 | 8 May 2023 | The issue was addressed with improved checks | Grouped by weakness | 6.8 |
| CVE-2023-27956 | 8 May 2023 | The issue was addressed with improved memory handling | Grouped by weakness | 6.9 |
| CVE-2023-41064KEV | 7 Sep 2023 | Apple iOS, iPadOS, and macOS ImageIO Buffer Overflow Vulnerability | Grouped by weakness | 68.3 |
| CVE-2024-23286 | 8 Mar 2024 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 20.7 |
| CVE-2024-27878 | 29 Jul 2024 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 9.7 |
| CVE-2024-44144 | 28 Oct 2024 | A buffer overflow was addressed with improved size validation | Grouped by weakness | 8.4 |
| CVE-2024-44218 | 28 Oct 2024 | This issue was addressed with improved checks | Grouped by weakness | 10.0 |
| CVE-2024-44232 | 1 Nov 2024 | The issue was addressed with improved bounds checks | Grouped by weakness | 10.4 |
| CVE-2024-44233 | 1 Nov 2024 | The issue was addressed with improved bounds checks | Grouped by weakness | 10.4 |
| CVE-2024-44234 | 1 Nov 2024 | The issue was addressed with improved bounds checks | Grouped by weakness | 10.4 |
| CVE-2024-44306 | 19 Nov 2024 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 7.0 |
| CVE-2024-44307 | 19 Nov 2024 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 7.0 |
| CVE-2025-24131 | 27 Jan 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 18.5 |
| CVE-2025-24153 | 27 Jan 2025 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 7.8 |
| CVE-2025-24157 | 31 Mar 2025 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 14.8 |
| CVE-2025-24209 | 31 Mar 2025 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 16.8 |
| CVE-2025-24237 | 31 Mar 2025 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 22.1 |
| CVE-2025-31223 | 12 May 2025 | The issue was addressed with improved checks | Grouped by weakness | 15.2 |
| 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-31277KEV | 30 Jul 2025 | Apple Multiple Products Buffer Overflow Vulnerability | Grouped by weakness | 69.5 |
| CVE-2025-43312 | 15 Sep 2025 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 7.3 |
| CVE-2025-43433 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 19.6 |
| CVE-2025-43441 | 4 Nov 2025 | The issue was addressed with improved memory handling | Grouped by weakness | 15.3 |
| CVE-2025-43520KEV | 12 Dec 2025 | Apple Multiple Products Classic Buffer Overflow Vulnerability | Grouped by weakness | 59.2 |
| CVE-2025-43532 | 12 Dec 2025 | A memory corruption issue was addressed with improved bounds checking | Grouped by weakness | 47.5 |
| CVE-2025-43501 | 17 Dec 2025 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 14.1 |
| CVE-2026-20608 | 11 Feb 2026 | This issue was addressed through improved state management | Grouped by weakness | 7.8 |
| 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-20652 | 11 Feb 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 15.9 |
| CVE-2023-43010 | 12 Mar 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 18.3 |
| CVE-2026-20664 | 25 Mar 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 14.0 |
| CVE-2026-28857 | 25 Mar 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 14.9 |
| CVE-2026-28858 | 25 Mar 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 16.1 |
| CVE-2026-28859 | 25 Mar 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 13.3 |
| CVE-2026-28875 | 25 Mar 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 13.7 |
| 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-28925 | 11 May 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 12.9 |
| 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-28959 | 11 May 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 15.0 |
| CVE-2026-39869 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 7.1 |
| CVE-2026-43658 | 11 May 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 10.2 |
| CVE-2026-43776 | 27 Jul 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 7.3 |
| CVE-2026-43807 | 27 Jul 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 17.7 |
| CVE-2026-64722 | 27 Jul 2026 | A buffer overflow issue was addressed with improved memory handling | Grouped by weakness | 5.4 |
| CVE-2026-64747 | 27 Jul 2026 | A buffer overflow was addressed with improved size validation | Grouped by weakness | 12.3 |
| CVE-2026-64767 | 27 Jul 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 18.8 |
| CVE-2026-64705 | 25 Aug 2026 | A buffer overflow was addressed with improved bounds checking | Grouped by weakness | 10.1 |
| CVE-2026-65357 | 14 Sep 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 6.8 |
| CVE-2026-65398 | 14 Sep 2026 | An out-of-bounds access issue was addressed with improved bounds checking | Grouped by weakness | 6.1 |
| CVE-2026-84497 | 14 Sep 2026 | A buffer overflow was addressed with improved size validation | Grouped by weakness | 7.1 |
| CVE-2026-84609 | 14 Sep 2026 | A permissions issue was addressed with improved path validation | Grouped by weakness | 17.2 |
| CVE-2026-84632 | 14 Sep 2026 | The issue was addressed with improved memory handling | Grouped by weakness | 6.3 |