| CVE-2026-43670 | 8.8 | high | apple / safari | A Content Security Policy bypass was addressed with improved enforcement in AudioWorklet contexts. | 11d ago |
| CVE-2026-65346 | 8.8 | high | apple / ipados | An integer overflow was addressed with improved input validation. | 19d ago |
| CVE-2026-43794 | 8.8 | high | apple / safari | A memory corruption issue was addressed with improved memory handling. | 19d ago |
| CVE-2026-64783 | 8.8 | high | apple / safari | A use-after-free issue was addressed with improved memory management. | 40d ago |
| CVE-2026-64757 | 8.8 | high | apple / safari | A memory corruption issue was addressed with improved state management. | 40d ago |
| CVE-2026-64739 | 8.8 | high | apple / ipados | An out-of-bounds write issue was addressed with improved bounds checking. | 40d ago |
| CVE-2026-43818 | 8.8 | high | apple / ipados | An integer overflow was addressed with improved input validation. | 40d ago |
| CVE-2026-28931 | 8.8 | high | apple / ipados | A buffer overflow was addressed with improved bounds checking. | 40d ago |
| CVE-2026-43731 | 8.8 | high | apple / safari | A use-after-free issue was addressed with improved memory management. | 68d ago |
| CVE-2026-43715 | 8.8 | high | apple / safari | A use-after-free issue was addressed with improved memory management. | 68d ago |
| CVE-2026-43705 | 8.8 | high | apple / safari | A type confusion issue was addressed with improved checks. | 68d ago |
| CVE-2025-24284 | 8.8 | high | apple / macos | This issue was addressed with improved checks to prevent unauthorized actions. | 86d ago |
| CVE-2025-43524 | 8.8 | high | apple / macos | An access issue was addressed with additional sandbox restrictions. | 116d ago |
| CVE-2026-28995 | 8.8 | high | apple / ipados | A logic issue was addressed with improved restrictions. | 117d ago |
| CVE-2026-28978 | 8.8 | high | apple / macos | A permissions issue was addressed with additional restrictions. | 117d ago |
| CVE-2026-28955 | 8.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 117d ago |
| CVE-2026-28947 | 8.8 | high | apple / ipados | A use-after-free issue was addressed with improved memory management. | 117d ago |
| CVE-2026-28940 | 8.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 117d ago |
| CVE-2026-28923 | 8.8 | high | apple / macos | A logging issue was addressed with improved data redaction. | 117d ago |
| CVE-2026-28847 | 8.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 117d ago |
| CVE-2023-43010 | 8.8 | high | apple / safari | The issue was addressed with improved memory handling. | 178d ago |
| CVE-2026-43760 | 8.6 | high | apple / macos | An access issue was addressed with improved access restrictions. | 40d ago |
| CVE-2026-28973 | 8.6 | high | apple / ipados | An integer overflow was addressed with improved input validation. | 40d ago |
| CVE-2026-64737 | 8.2 | high | apple / macos | An authorization issue was addressed with improved state management. | 40d ago |
| CVE-2026-43772 | 8.2 | high | apple / macos | A path traversal issue was addressed with improved input validation. | 40d ago |
| CVE-2026-64768 | 8.1 | high | apple / ipados | An out-of-bounds read issue was addressed with improved input validation. | 40d ago |
| CVE-2026-64719 | 8.1 | high | apple / safari | An out-of-bounds access issue was addressed with improved bounds checking. | 40d ago |
| CVE-2026-64713 | 8.1 | high | apple / safari | This issue was addressed with improved checks. | 40d ago |
| CVE-2026-43735 | 8.1 | high | apple / safari | The issue was addressed with improved checks. | 68d ago |
| CVE-2026-28907 | 8.1 | high | apple / ipados | The issue was addressed with improved input validation. | 117d ago |
| CVE-2026-64766 | 7.8 | high | apple / ipados | An integer overflow was addressed with improved input validation. | 40d ago |
| CVE-2026-64765 | 7.8 | high | apple / ipados | An integer overflow was addressed with improved input validation. | 40d ago |
| CVE-2026-64764 | 7.8 | high | apple / ipados | An out-of-bounds write issue was addressed with improved bounds checking. | 40d ago |
| CVE-2026-64763 | 7.8 | high | apple / ipados | An out-of-bounds write issue was addressed by removing the vulnerable code. | 40d ago |
| CVE-2026-64758 | 7.8 | high | apple / ipados | The issue was addressed with improved bounds checks. | 40d ago |
| CVE-2026-64749 | 7.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-64747 | 7.8 | high | apple / ipados | A buffer overflow was addressed with improved size validation. | 40d ago |
| CVE-2026-64716 | 7.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-43780 | 7.8 | high | apple / ipados | An integer overflow was addressed with improved input validation. | 40d ago |
| CVE-2026-43776 | 7.8 | high | apple / ipados | A buffer overflow was addressed with improved bounds checking. | 40d ago |
| CVE-2026-43749 | 7.8 | high | apple / macos | A parsing issue in the handling of directory paths was addressed with improved path validation. | 40d ago |
| CVE-2026-43733 | 7.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-43729 | 7.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-43723 | 7.8 | high | apple / ipados | A path handling issue was addressed with improved validation. | 40d ago |
| CVE-2026-43711 | 7.8 | high | apple / ipados | A memory corruption issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-43698 | 7.8 | high | apple / macos | An injection issue was addressed with improved validation. | 40d ago |
| CVE-2026-43673 | 7.8 | high | apple / ipados | The issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-39877 | 7.8 | high | apple / macos | A memory corruption issue was addressed with improved memory handling. | 40d ago |
| CVE-2026-39875 | 7.8 | high | apple / macos | A permissions issue was addressed with additional restrictions. | 40d ago |
| CVE-2026-39874 | 7.8 | high | apple / macos | A permissions issue was addressed with additional restrictions. | 40d ago |
| CVE-2026-28981 | 7.8 | high | apple / macos | A buffer overflow was addressed with improved bounds checking. | 40d ago |
| CVE-2026-28912 | 7.8 | high | apple / macos | A logic issue was addressed with improved restrictions. | 40d ago |
| CVE-2026-43724 | 7.8 | high | apple / ipados | The issue was addressed with improved input sanitization. | 68d ago |
| CVE-2025-31272 | 7.8 | high | apple / macos | The issue was addressed with improved checks. | 86d ago |
| CVE-2025-43306 | 7.8 | high | apple / macos | A logic issue was addressed with improved checks. | 102d ago |
| CVE-2026-28951 | 7.8 | high | apple / ipados | An authorization issue was addressed with improved state management. | 117d ago |
| CVE-2026-28919 | 7.8 | high | apple / macos | A consistency issue was addressed with improved state handling. | 117d ago |
| CVE-2026-28915 | 7.8 | high | apple / macos | A parsing issue in the handling of directory paths was addressed with improved path validation. | 117d ago |
| CVE-2026-28840 | 7.8 | high | apple / macos | A permissions issue was addressed with additional restrictions. | 117d ago |
| CVE-2026-28896 | 7.7 | high | apple / macos | The issue was addressed with improved memory handling. | 40d ago |
