macOS
Apple- Product type
- Operating system
- Catalog vulnerabilities
- 3,487
Severity across 392 analyzed records
en
Severity across 392 analyzed records
Verify to analyze this security profile
As of 09/12/2026, within CyStack's analyzed data, macOS has 191 security vulnerabilities published in the last 90 days. Of these, 94 are rated High or Critical. Notably, 1 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 macOS and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-64705 | Exploitation statusNot known exploited | FixYes | Published08/25/2026 | SeverityMedium |
CVE-2026-43670 | Exploitation statusNot known exploited | FixYes | Published08/25/2026 | SeverityHigh |
CVE-2026-20679 | Exploitation statusNot known exploited | FixYes | Published08/21/2026 | SeverityMedium |
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-65346 | 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-65347 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-43795 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65330 | 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-64788 | 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-65339 | 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-65343 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityHigh |
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-43667 | 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-65349 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-65400 | Exploitation statusKEV | FixYes | Published08/06/2026 | SeverityCritical |
CVE-2026-43757 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64737 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43782 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43805 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-39873 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64776 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43813 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64721 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-20672 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64740 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64691 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43673 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64783 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43809 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43665 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43777 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43799 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43776 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-28900 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43672 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43760 | Exploitation statusPublic exploit | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64716 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-28982 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64700 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64757 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64720 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-28849 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43812 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43804 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43756 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64707 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64711 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64746 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43767 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64697 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43730 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-28911 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43819 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43771 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43747 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-28931 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43710 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64731 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64766 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43803 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-39875 | Exploitation statusPublic exploit | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64770 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64727 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43792 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43793 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64726 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43681 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64771 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43814 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-39874 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64767 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43802 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64730 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43711 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43750 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-28926 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43770 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43818 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64696 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43766 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-28896 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan