watchOS
Apple- Product type
- Other
- Catalog vulnerabilities
- 1,955
Severity across 249 analyzed records
en
Verify to analyze this security profile
As of 09/12/2026, within CyStack's analyzed data, watchOS has 103 security vulnerabilities published in the last 90 days. Of these, 50 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 watchOS and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-43679 | Exploitation statusNot known exploited | FixYes | Published08/21/2026 | SeverityLow |
CVE-2026-28984 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-43667 | Exploitation statusNot known exploited | FixYes | Published08/17/2026 | SeverityMedium |
CVE-2026-43805 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
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-43673 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64783 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43799 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64741 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64716 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
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-64746 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43730 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-28931 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
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-64726 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43814 | 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-28896 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43822 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64747 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64751 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64729 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
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-64725 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43817 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-39877 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43801 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64764 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43769 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64733 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64709 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-28973 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43744 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43800 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64765 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43816 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64724 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-28928 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64728 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43796 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43807 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43780 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64735 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43714 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64719 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64758 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64739 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64693 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64742 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43759 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64754 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43758 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64743 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64692 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43723 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-64718 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64734 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-64763 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityHigh |
CVE-2026-43739 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityMedium |
CVE-2026-43810 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-64775 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43778 | Exploitation statusNot known exploited | FixYes | Published07/27/2026 | SeverityCritical |
CVE-2026-43700 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-43720 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
CVE-2026-39868 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityCritical |
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-43706 | 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-43724 | 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-43743 | Exploitation statusNot known exploited | FixYes | Published06/29/2026 | SeverityMedium |
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 |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan