CVE-2026-43805: Apple macOS race condition (CVSS 9.8)

Description

A race condition was addressed with improved state handling. This issue is fixed in iOS 26.6 and iPadOS 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, watchOS 26.6. An app may be able to cause unexpected system termination or write kernel memory.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Apple iPadOS< 26.6

Apple iPhone OS< 26.6

Apple macOS≥ 14.0 < 14.8.8 · ≥ 15.0 < 15.7.8 · ≥ 26.0 < 26.6

Apple Watchos< 26.6

Remediation

Fixed in

Apple iPadOS≥ 26.6

Apple iPhone OS≥ 26.6

Apple macOS≥ 14.8.8

Apple Watchos≥ 26.6

Patch & vendor advisories

References

https://support.apple.com/en-us/128066Release NotesVendor Advisory
https://support.apple.com/en-us/128067Release NotesVendor Advisory
https://support.apple.com/en-us/128068Release NotesVendor Advisory
https://support.apple.com/en-us/128071Release NotesVendor Advisory
https://support.apple.com/en-us/128072Release NotesVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-43805 being actively exploited?

CVE-2026-43805 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.47%.

How severe is CVE-2026-43805?

CVE-2026-43805 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.47% probability of exploitation.

Which products are affected by CVE-2026-43805?

Affected products include Apple iPadOS, Apple iPhone OS, Apple macOS, Apple Watchos.

How do I fix CVE-2026-43805?

Upgrade affected software to a fixed version, for example Apple iPadOS 26.6, Apple iPhone OS 26.6, Apple macOS 14.8.8 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-43805 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo