Safari
Apple- Product type
- Web browser
- Catalog vulnerabilities
- 1,687
Severity across 217 analyzed records
en
Severity across 217 analyzed records
Verify to analyze this security profile
As of 09/12/2026, within CyStack's analyzed data, Safari has 64 security vulnerabilities published in the last 90 days. Of these, 12 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Safari and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-43670 | Exploitation statusNot known exploited | FixYes | Published08/25/2026 | SeverityHigh |
CVE-2026-65331 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-43794 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityHigh |
CVE-2026-65351 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64782 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityLow |
CVE-2026-43795 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65340 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65337 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65336 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64784 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65341 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-28984 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64787 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65335 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65334 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65338 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65333 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64778 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64781 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64715 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64780 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64779 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityLow |
CVE-2026-65332 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-64783 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64757 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43804 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43792 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64730 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43821 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64713 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64728 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64719 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64718 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43700 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43716 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43720 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43721 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-39872 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43717 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43740 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43701 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityHigh |
CVE-2026-43663 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43726 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43746 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43707 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43727 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43731 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityHigh |
CVE-2026-43732 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43708 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43712 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43745 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43704 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43705 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityHigh |
CVE-2026-43713 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43709 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43699 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43676 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43725 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityHigh |
CVE-2026-43734 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43718 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-28979 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43735 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityHigh |
CVE-2026-43742 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43715 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityHigh |
CVE-2026-28917 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityMedium |
CVE-2026-28901 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28946 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28907 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28971 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityMedium |
CVE-2026-28947 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-43658 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28905 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28913 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28944 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28883 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-43660 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28904 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28953 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28958 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityMedium |
CVE-2026-28962 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28903 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28942 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28902 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28847 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-28955 | Exploitation statusNot known exploited | FixYes | Published05/11/2026 | SeverityHigh |
CVE-2026-20691 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityMedium |
CVE-2026-20664 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityHigh |
CVE-2026-20665 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityMedium |
CVE-2026-28859 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityHigh |
CVE-2026-28861 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityMedium |
CVE-2026-28857 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityHigh |
CVE-2026-28871 | Exploitation statusNot known exploited | FixYes | Published03/25/2026 | SeverityMedium |
CVE-2026-20643 | Exploitation statusNot known exploited | FixYes | Published03/17/2026 | SeverityMedium |
CVE-2023-43010 | Exploitation statusNot known exploited | FixYes | Published03/12/2026 | SeverityHigh |
CVE-2026-20644 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityHigh |
CVE-2026-20652 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityHigh |
CVE-2026-20608 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityHigh |
CVE-2026-20635 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityHigh |
CVE-2026-20660 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityMedium |
CVE-2026-20676 | Exploitation statusNot known exploited | FixYes | Published02/11/2026 | SeverityMedium |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan