Class familyApple · iOS
Apple iOS and macOS type confusion flaws, 2019–2026
40 iOS CVEs with CWE-843 weaknesses, 18 Dec 2019 to 26 Oct 2026. 8 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 2019’19
1 2020’20
2 2021’21
5 2022’22
2 2023’23
6 2024’24
9 2025’25
14 2026’26
In CISA KEVNot in KEV
20191 CVE, 1 in KEV
20201 CVE, 1 in KEV
20212 CVEs, 2 in KEV
20225 CVEs, 1 in KEV
20232 CVEs, 2 in KEV
20246 CVEs, 1 in KEV
20259 CVEs
202614 CVEs
CVEs in this family
Table view of the years above| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2019-8506KEV | 18 Dec 2019 | Apple Multiple Products Type Confusion Vulnerability | Grouped by weakness | 68.5 |
| CVE-2020-27932KEV | 8 Dec 2020 | Apple Multiple Products Type Confusion Vulnerability | Grouped by weakness | 67.6 |
| CVE-2021-1789KEV | 2 Apr 2021 | Apple Multiple Products Type Confusion Vulnerability | Grouped by weakness | 67.3 |
| CVE-2021-30869KEV | 24 Aug 2021 | Apple iOS, iPadOS, and macOS Type Confusion Vulnerability | Grouped by weakness | 65.5 |
| CVE-2022-32814 | 23 Sep 2022 | A type confusion issue was addressed with improved state handling | Grouped by weakness | 9.7 |
| CVE-2022-32915 | 1 Nov 2022 | A type confusion issue was addressed with improved checks | Grouped by weakness | 9.7 |
| CVE-2022-42823 | 1 Nov 2022 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 21.9 |
| CVE-2022-42841 | 15 Dec 2022 | A type confusion issue was addressed with improved checks | Grouped by weakness | 11.9 |
| CVE-2022-42856KEV | 15 Dec 2022 | Apple iOS Type Confusion Vulnerability | Grouped by weakness | 63.2 |
| CVE-2023-23529KEV | 27 Feb 2023 | Apple Multiple Products WebKit Type Confusion Vulnerability | Grouped by weakness | 63.2 |
| CVE-2023-32439KEV | 23 Jun 2023 | Apple Multiple Products WebKit Type Confusion Vulnerability | Grouped by weakness | 63.7 |
| CVE-2023-41060 | 10 Jan 2024 | A type confusion issue was addressed with improved checks | Grouped by weakness | 20.1 |
| CVE-2023-41075 | 10 Jan 2024 | A type confusion issue was addressed with improved checks | Grouped by weakness | 7.7 |
| CVE-2024-23222KEV | 23 Jan 2024 | Apple Multiple Products WebKit Type Confusion Vulnerability | Grouped by weakness | 68.3 |
| CVE-2024-40788 | 29 Jul 2024 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 9.2 |
| CVE-2024-40803 | 29 Jul 2024 | A type confusion issue was addressed with improved checks | Grouped by weakness | 19.0 |
| CVE-2024-54505 | 11 Dec 2024 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 17.5 |
| CVE-2025-24129 | 27 Jan 2025 | A type confusion issue was addressed with improved checks | Grouped by weakness | 19.4 |
| CVE-2025-24137 | 27 Jan 2025 | A type confusion issue was addressed with improved checks | Grouped by weakness | 17.9 |
| CVE-2025-24213 | 31 Mar 2025 | This issue was addressed with improved handling of floats | Grouped by weakness | 12.9 |
| CVE-2025-24271 | 29 Apr 2025 | An access issue was addressed with improved access restrictions | Grouped by weakness | 17.5 |
| CVE-2025-30445 | 29 Apr 2025 | A type confusion issue was addressed with improved checks | Grouped by weakness | 10.9 |
| CVE-2025-31206 | 12 May 2025 | A type confusion issue was addressed with improved state handling | Grouped by weakness | 15.6 |
| CVE-2025-43297 | 15 Sep 2025 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 10.5 |
| CVE-2025-43355 | 15 Sep 2025 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 6.8 |
| CVE-2025-43541 | 17 Dec 2025 | A type confusion issue was addressed with improved state handling | Grouped by weakness | 27.7 |
| CVE-2026-28822 | 25 Mar 2026 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 6.6 |
| CVE-2025-43236 | 2 Apr 2026 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 3.8 |
| CVE-2026-28983 | 11 May 2026 | A type confusion issue was addressed with improved checks | Grouped by weakness | 16.6 |
| CVE-2026-43705 | 29 Jun 2026 | A type confusion issue was addressed with improved checks | Grouped by weakness | 13.5 |
| CVE-2026-64693 | 27 Jul 2026 | A type confusion issue was addressed with improved checks | Grouped by weakness | 4.9 |
| CVE-2026-64704 | 27 Jul 2026 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 16.5 |
| CVE-2026-64727 | 27 Jul 2026 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 15.4 |
| CVE-2026-65409 | 14 Sep 2026 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 5.3 |
| CVE-2026-84602 | 14 Sep 2026 | A type confusion issue was addressed with improved checks | Grouped by weakness | 4.8 |
| CVE-2026-84635 | 14 Sep 2026 | A logic issue was addressed with improved state management | Grouped by weakness | 10.7 |
| CVE-2026-86872 | 20 Oct 2026 | A logic issue was addressed with improved state management | Grouped by weakness | 7.5 |
| CVE-2026-86922 | 20 Oct 2026 | A type confusion issue was addressed with improved state management | Grouped by weakness | 11.5 |
| CVE-2026-112547 | 26 Oct 2026 | A type confusion issue was addressed with improved checks | Grouped by weakness | 4.5 |
| CVE-2026-112659 | 26 Oct 2026 | A type confusion issue was addressed with improved memory handling | Grouped by weakness | 15.4 |