Apple Security Updates July
| Update and details | Supported devices | Released on |
|---|---|---|
| iOS 26.6 and iPadOS 26.6 | Compatible with iPhone 11 and newer, iPad Pro 12.9-inch (3rd generation onward), iPad Pro 11-inch (1st generation onward), iPad Air (3rd generation onward), iPad (8th generation onward), and iPad mini (5th generation onward) | July 27, 2026 |
| macOS Tahoe 26.6 | Runs on macOS Tahoe | July 27, 2026 |
| macOS Sequoia 15.7.8 | Runs on macOS Sequoia | July 27, 2026 |
| macOS Sonoma 14.8.8 | Runs on macOS Sonoma | July 27, 2026 |
| tvOS 26.6 | Works with all Apple TV HD and Apple TV 4K models | July 27, 2026 |
| watchOS 26.6 | Supports Apple Watch Series 6 and newer | July 27, 2026 |
| visionOS 26.6 | Supports all Apple |
| Accounts Framework | macOS Tahoe | An app could uniquely identify (fingerprint) the user | This was resolved by strengthening data protection safeguards. | CVE-2026-64733 |
| afpfs | macOS Tahoe | A remote attacker could crash the system or corrupt kernel memory | A buffer overflow has been closed off with stricter bounds checking. | CVE-2026-64767 |
| apache | macOS Tahoe | A remote attacker could trigger a denial-of-service condition | This stems from an issue in third-party open-source code that Apples software also incorporates; the CVE ID was assigned externally, and further detail is available at cve.org. | CVE-2026-23918 |
| APFS | macOS Tahoe | A remote user could crash the system or corrupt kernel memory | This was resolved through more careful memory handling. | CVE-2026-64695 |
| App Store | macOS Tahoe | An app could reach sensitive user data it shouldnt | This was fixed with more rigorous checks. | CVE-2026-43801 |
| Apple Account | macOS Tahoe | An app could gain access to a users sensitive data | A race condition was resolved by handling state more carefully. | CVE-2026-43781 |
| Apple Account | macOS Tahoe | A malicious app could escape its sandbox | An authorization gap was corrected through better state management. | CVE-2026-64737 |
| Apple Neural Engine | macOS Tahoe | An app could trigger an unexpected system shutdown | An out-of-bounds write was prevented by tightening bounds checks. | CVE-2026-43748 |
| Apple Neural Engine | macOS Tahoe | An app could force the system to crash unexpectedly | A use-after-free flaw was corrected through improved memory management. | CVE-2026-28928 |
| AppleDouble | macOS Tahoe | Opening a specially crafted file could crash the app or allow arbitrary code to run | Tighter bounds checking now prevents a buffer overflow that existed here. | CVE-2026-43776 |
| AppleRAID | macOS Tahoe | A local user could read the contents of kernel memory | A buffer-overflow condition was corrected by enforcing stricter bounds checks. | CVE-2026-43681 |
| Assets | macOS Tahoe | A malicious app could get around a users Privacy settings | Improved state management now closes an authorization weakness here. | CVE-2026-43672 |
| ATS | macOS Tahoe | An app could read files outside the bounds of its sandbox | A permissions flaw was eliminated by removing the responsible code. | CVE-2026-43763 |
| Audio | macOS Tahoe | An app could escape its sandbox | Tighter sandbox restrictions now close an access-control weakness here. | CVE-2026-64702 |
| Audio | macOS Tahoe | An app could trigger a denial-of-service condition | Stricter bounds checking now blocks an out-of-bounds write that was possible here. | CVE-2026-64725 |
| AuthKit | macOS Tahoe | An app could uniquely identify (fingerprint) the user | A permissions gap was closed off with tighter restrictions. | CVE-2026-43730 |
| AVEVideoEncoder | macOS Tahoe | An app could run arbitrary code with kernel-level privileges | A buffer overflow was resolved by validating sizes more carefully. | CVE-2026-64747 |
| AVEVideoEncoder | macOS Tahoe | An app could trigger an unexpected system shutdown | An out-of-bounds read was closed off with stricter bounds checking. | CVE-2026-64762 |
| BackgroundAssets | macOS Tahoe | An app could delete files it lacks permission for | A permissions flaw was fixed through stricter validation. | CVE-2026-64707 |
| cd9660 | macOS Tahoe | An app could trigger a system crash or read kernel memory | More careful memory handling now closes this gap. | CVE-2026-64698 |
| CloudAttestation | macOS Tahoe | A specially crafted app could get around code-signing checks | A validation gap was closed by sanitizing input more thoroughly. | CVE-2026-43813 |
| Contacts | macOS Tahoe | An app could add contacts without the users consent | An authorization weakness was fixed with stricter validation. | CVE-2026-64746 |
| Contacts | macOS Tahoe | A specially crafted contact entry could leak sensitive data | This was resolved with more thorough checks. | CVE-2026-64734 |
| Contacts | macOS Tahoe | An app could access details about a users contacts | More thorough checks now close this gap. | CVE-2026-43797 |
| Control Center | macOS Tahoe | An app could access a users sensitive data | A logic flaw was corrected with stricter validation. | CVE-2026-43756 |
| Core Services | macOS Tahoe | An app could obtain root-level access | Better state handling now prevents a timing-related race condition here. | CVE-2026-43693 |
| CoreAudio | macOS Tahoe | Opening a specially crafted audio file could corrupt process memory | This was corrected with improvements to memory handling. | CVE-2026-43673 |
| CoreAudio | macOS Tahoe | A specially crafted media file could crash the process while its audio stream plays | An out-of-bounds write condition has been closed with improved bounds checking. | CVE-2026-43744 |
| CoreAudio | macOS Tahoe | A remote attacker could trigger an unexpected system shutdown | An out-of-bounds write was prevented by tightening bounds checks. | CVE-2026-43803 |
| CoreMedia | macOS Tahoe | An app could reach sensitive user data it shouldnt | An authorization gap was corrected through better state management. | CVE-2026-43775, CVE-2026-43759 |
| CoreMedia | macOS Tahoe | Opening a specially crafted video file could crash the app | A memory-corruption flaw was corrected through more careful memory handling. | CVE-2026-43711 |
| CoreVideo | macOS Tahoe | An app could force the system to crash unexpectedly | Stricter bounds checking now blocks an out-of-bounds write that was possible here. | CVE-2026-43802 |
| Crash Reporter | macOS Tahoe | An app could leak a users sensitive information | A privacy gap was closed by no longer retaining the sensitive data in question. | CVE-2026-64710 |
| CUPS | macOS Tahoe | A malicious app could escalate to root-level privileges | Additional restrictions now prevent a permissions weakness that existed here. | CVE-2026-39875 |
| CUPS | macOS Tahoe | An app could escalate to root-level privileges | An injection vulnerability was closed off with stricter validation. | CVE-2026-43698 |
| curl | macOS Tahoe | Login credentials could be transmitted to a server on a different origin than intended | The underlying flaw lives in open-source code used by Apples software as well. A third party issued the CVE ID; see cve.org for more. | CVE-2026-3784, CVE-2026-3783 |
| Data Detectors UI | macOS Tahoe | An app could gain access to a user's sensitive data | Improved state management now closes an authorization weakness here. | CVE-2026-43758 |
| DesktopServices | macOS Tahoe | An app could get around Gatekeeper checks | A way of bypassing file quarantine has been closed off with added checks. | CVE-2026-64708 |
| Disk Images | macOS Tahoe | An app could expose the contents of kernel memory | This was resolved by tightening bounds checks. | CVE-2026-64776 |
| Disk Images | macOS Tahoe | An app could trigger an unexpected system shutdown | An integer overflow was closed off through stricter input validation. | CVE-2026-64694 |
| Disk Images | macOS Tahoe | Parsing a specially crafted file could crash the app | Improved bounds checking now prevents an out-of-bounds read that was possible here. | CVE-2026-43747 |
| Disk Images | macOS Tahoe | An app could get around network restrictions | A permissions gap was closed by tightening sandbox restrictions. | CVE-2026-28945 |
| DriverKit | macOS Tahoe | An app could force the system to crash unexpectedly | Environment variables werent being handled safely; tighter validation now closes the gap. | CVE-2026-43793 |
| DriverKit | macOS Tahoe | Someone with physical access to a locked device could view a users sensitive information | An out-of-bounds read was closed off with stricter bounds checking. | CVE-2026-43753 |
| Foundation | macOS Tahoe | A malicious app could access a users protected data | This was resolved by sanitizing input more thoroughly. | CVE-2026-43714 |
| Game Center | macOS Tahoe | A malicious app could escape its sandbox | A flaw in how directory paths were interpreted has been closed with more rigorous path validation. | CVE-2026-64740 |
| Game Center | macOS Tahoe | An app could reach sensitive user data it shouldnt | This was resolved by strengthening data protection safeguards. | CVE-2026-43796 |
| GPU Drivers | macOS Tahoe | An app could trigger an unexpected system shutdown | A buffer overflow was resolved by validating sizes more carefully. | CVE-2026-64691 |
| Heimdal | macOS Tahoe | An app could trigger a denial-of-service condition | Improved bounds checking now prevents an out-of-bounds read that was possible here. | CVE-2026-64692 |
| HFS | macOS Tahoe | A remote user could trigger a system crash or damage kernel memory | This was resolved through more careful memory handling. | CVE-2026-43682 |
| HFS | macOS Tahoe | Opening a specially crafted image could allow arbitrary code to run | A buffer overflow has been closed off with stricter bounds checking. | CVE-2026-28981 |
| HFS | macOS Tahoe | Mounting a specially crafted disk image could crash the system or corrupt kernel memory | An out-of-bounds read was closed off with stricter bounds checking. | CVE-2026-43773 |
| HFS | macOS Tahoe | An app could force the system to crash unexpectedly | More careful memory handling now closes this gap. | CVE-2026-43767 |
| HFS | macOS Tahoe | An app could trigger an unexpected system shutdown | More careful input validation now prevents an integer overflow that was possible here. | CVE-2026-43764 |
| HFS | macOS Tahoe | An app could crash the system or corrupt kernel memory | This was corrected with improvements to memory handling. | CVE-2026-64697 |
| HFS | macOS Tahoe | An attacker could crash the system or corrupt kernel memory | This was resolved through more careful memory handling. | CVE-2026-43710 |
| ImageIO | macOS Tahoe | Processing a specially crafted texture could crash the app | An integer overflow was closed off through stricter input validation. | CVE-2026-43780 |
| ImageIO | macOS Tahoe | Opening a specially crafted image could allow arbitrary code to run | More careful input validation now prevents an integer overflow that was possible here. | CVE-2026-43818 |
| ImageIO | macOS Tahoe | Opening a specially crafted image could corrupt process memory | More careful memory handling now closes this gap. | CVE-2026-64716 |
| ImageIO | macOS Tahoe | Opening a specially crafted file could crash the app | This was resolved by tightening bounds checks. | CVE-2026-64758 |
| ImageIO | macOS Tahoe | Opening a specially crafted file could trigger a denial-of-service condition | An out-of-bounds write condition has been closed with improved bounds checking. | CVE-2026-64754 |
| ImageIO | macOS Tahoe | Opening a specially crafted image could trigger a denial-of-service condition | A type-confusion flaw was corrected with more thorough checks. | CVE-2026-64693 |
| IOKit | macOS Tahoe | An app could trigger a system crash or write to kernel memory | A race condition was resolved by handling state more carefully. | CVE-2026-43805 |
| Kernel | macOS Tahoe | An app could gain access to a user's sensitive data | This was fixed with more rigorous checks. | CVE-2026-43782 |
| Kernel | macOS Tahoe | An app could trigger a system crash or damage kernel memory | This was corrected with improvements to memory handling. | CVE-2026-64749 |
| Kernel | macOS Tahoe | An app could leak kernel memory contents | An information leak was closed off with added validation. | CVE-2026-64744 |
| Kernel | macOS Tahoe | An app could crash the system or corrupt kernel memory | Better memory management now prevents a use-after-free condition that existed here. | CVE-2026-43778 |
| Kernel | macOS Tahoe | A remote user could crash the system or corrupt kernel memory | A race condition was resolved by improving how locking is handled. | CVE-2026-28982 |
| Kernel | macOS Tahoe | An app could expose the contents of kernel memory | This was resolved through more careful memory handling. | CVE-2026-64709 |
| Kernel | macOS Tahoe | A remote attacker could get around network filters | An interface-consistency flaw was corrected through improved state management. | CVE-2026-64735 |
| Kernel | macOS Tahoe | An app could force the system to crash unexpectedly | An out-of-bounds write was prevented by tightening bounds checks. | CVE-2026-43739, CVE-2026-43816 |
| Kernel | macOS Tahoe | An app could trigger an unexpected system shutdown | A use-after-free flaw was corrected through improved memory management. | CVE-2026-43822, CVE-2026-64729, CVE-2026-43814, CVE-2026-64700, CVE-2026-43799 |
| Kernel | macOS Tahoe | Connecting to a malicious NFS server could corrupt kernel memory | Tighter bounds checking now prevents a buffer overflow that existed here. | CVE-2026-28931 |
| Kernel | macOS Tahoe | An app could force the system to crash unexpectedly | Improved bounds checking now prevents an out-of-bounds read that was possible here. | CVE-2026-43817, CVE-2026-43809, CVE-2026-43757 |
| Kernel | macOS Tahoe | An app could trigger an unexpected system shutdown | An integer overflow was closed off through stricter input validation. | CVE-2026-43769 |
| Kernel | macOS Tahoe | An app could force the system to crash unexpectedly | A type-confusion flaw was corrected through more careful memory handling. | CVE-2026-64727 |
| Kernel | macOS Tahoe | A remote user could trigger a system crash or damage kernel memory | More careful memory handling now closes this gap. | CVE-2026-43810 |
| Kernel | macOS Tahoe | An app could trigger an unexpected system shutdown | A memory-initialization flaw was corrected through more careful memory handling. | CVE-2026-64775 |
| Kernel | macOS Tahoe | An app could reach sensitive user data it shouldn't | A logic flaw was corrected with more thorough checks. | CVE-2026-64723 |
| Kernel | macOS Tahoe | An app could force the system to crash unexpectedly | Better state handling now prevents a timing-related race condition here. | CVE-2026-64720 |
| Kernel | macOS Tahoe | An app could leak sensitive information about kernel state | This was fixed by redacting sensitive information more carefully. | CVE-2026-43754 |
| Kernel | macOS Tahoe | An app could trigger a system crash or write to kernel memory | Better memory management now prevents a use-after-free condition that existed here. | CVE-2026-64751 |
| Kernel | macOS Tahoe | An app could gain access to a user's sensitive data | This was resolved through better state management. | CVE-2026-64721 |
| libarchive | macOS Tahoe | Opening a specially crafted file could expose process memory contents | This traces back to an upstream open-source component that Apple also ships. The CVE ID came from an outside party — cve.org has additional details. | CVE-2026-4424 |
| libc | macOS Tahoe | A malicious app could escape its sandbox | More careful input validation now prevents an integer overflow that was possible here. | CVE-2026-28973 |
| Libnotify | macOS Tahoe | An attacker could crash the app unexpectedly | Stricter bounds checking now blocks an out-of-bounds write that was possible here. | CVE-2026-64739 |
| LoginWindow | macOS Tahoe | Someone with physical access to a locked device could view a user's sensitive information | An authorization gap was corrected through better state management. | CVE-2026-43766 |
| Managed Configuration | macOS Tahoe | An app could reach sensitive user data it shouldn't | Improved state management now closes an authorization weakness here. | CVE-2026-64743 |
| Maps | macOS Tahoe | A malicious app could escape its sandbox | A permissions gap was closed off with tighter restrictions. | CVE-2026-64738 |
| mDNSResponder | macOS Tahoe | A local attacker could trigger a denial-of-service condition | A denial-of-service flaw was eliminated by removing the responsible code. | CVE-2026-43806 |
| mDNSResponder | macOS Tahoe | An attacker on the local network could trigger a denial-of-service condition | This was corrected with improvements to memory handling. | CVE-2026-64724 |
| MediaRemote | macOS Tahoe | An app could obtain root-level access | A path-handling flaw was corrected with stricter validation. | CVE-2026-43723 |
| Metal | macOS Tahoe | A malicious app could corrupt the memory of a system process | This was resolved through more careful memory handling. | CVE-2026-28911 |
| Model I/O | macOS Tahoe | Opening a specially crafted image could corrupt process memory | More careful memory handling now closes this gap. | CVE-2026-43733, CVE-2026-43729 |
| Model I/O | macOS Tahoe | A remote attacker could crash the app or corrupt heap memory | An out-of-bounds write was fixed by validating input more thoroughly. | CVE-2026-64772 |
| Model I/O | macOS Tahoe | A remote attacker could crash the app or corrupt heap memory | A buffer-overflow condition was corrected by enforcing stricter bounds checks. | CVE-2026-64771 |
| Model I/O | macOS Tahoe | Loading a 3D model could expose process memory contents | A buffer-overflow flaw was corrected through more careful memory handling. | CVE-2026-64722 |
| Model I/O | macOS Tahoe | A remote attacker could crash the app or corrupt heap memory | An integer overflow was closed off through stricter input validation. | CVE-2026-64774 |
| Model I/O | macOS Tahoe | A remote attacker could crash the app or corrupt heap memory | An out-of-bounds write condition has been closed with improved bounds checking. | CVE-2026-64770, CVE-2026-64769 |
| Model I/O | macOS Tahoe | A remote attacker could cause the app to crash unexpectedly | An out-of-bounds read was corrected through more careful input validation. | CVE-2026-64768 |
| Net-SNMP | macOS Tahoe | An app could trigger a denial-of-service condition | A stack overflow was fixed through stricter input validation. | CVE-2026-43771 |
| NetFSFramework | macOS Tahoe | An app could escape its sandbox | A path-traversal flaw was fixed with stricter input validation. | CVE-2026-43772 |
| NSColorPanel | macOS Tahoe | An app could leak a user's sensitive information | This was fixed by adding entitlement checks. | CVE-2026-64711 |
| PackageKit | macOS Tahoe | A user could escalate their own privileges | A logic flaw was corrected by tightening restrictions. | CVE-2026-28912 |
| PackageKit | macOS Tahoe | An app could alter protected areas of the file system | This was fixed by handling symbolic links more carefully. | CVE-2026-43765 |
| Printing | macOS Tahoe | A malicious app could escape its sandbox | Improved validation now closes a path-handling weakness here. | CVE-2026-64731 |
| Pro Res | macOS Tahoe | An app could trigger an unexpected system shutdown | A use-after-free flaw was corrected through improved memory management. | CVE-2026-43812 |
| quarantine | macOS Tahoe | An app could trigger a system crash or write to kernel memory | This was corrected with improvements to memory handling. | CVE-2026-43694 |
| Remote Management | macOS Tahoe | A malicious app could obtain root-level access | Additional restrictions now prevent a permissions weakness that existed here. | CVE-2026-39874 |
| Safari | macOS Tahoe | An app could gain access to a users sensitive data | An authorization gap was corrected through better state management. | CVE-2026-43792 |
| SceneKit | macOS Tahoe | Opening a specially crafted file could crash the app or allow arbitrary code to run | More careful input validation now prevents an integer overflow that was possible here. | CVE-2026-64766, CVE-2026-64765 |
| SceneKit | macOS Tahoe | Opening a specially crafted file could crash the app or allow arbitrary code to run | An out-of-bounds write was prevented by tightening bounds checks. | CVE-2026-64764 |
| SceneKit | macOS Tahoe | Opening a specially crafted file could crash the app or allow arbitrary code to run | The out-of-bounds write was eliminated by removing the code responsible. | CVE-2026-64763 |
| Screen Sharing Server | macOS Tahoe | An app could intercept network traffic meant for a different process | A logic flaw was corrected by tightening restrictions. | CVE-2026-43779 |
| Screen Sharing Server | macOS Tahoe | A remote attacker could trigger a denial-of-service condition | This was fixed by strengthening input validation. | CVE-2026-43777 |
| Screen Sharing Server | macOS Tahoe | An app could access a user's sensitive data | An access-control gap was closed with stricter access restrictions. | CVE-2026-43760 |
| Security | macOS Tahoe | An attacker could alter the Keychain's state | This was resolved through better state management. | CVE-2026-43728 |
| SecurityAgent | macOS Tahoe | An app could escalate to root-level privileges | A race condition was corrected through improved state management. | CVE-2026-43755 |
| Siri | macOS Tahoe | Someone with physical access to a locked device could reach contacts and photos | This was fixed by adding further restrictions to the lock screen. | CVE-2026-64745 |
| Siri | macOS Tahoe | An app could reach sensitive user data it shouldn't | An information-disclosure flaw was eliminated by removing the responsible code. | CVE-2026-43800 |
| SMB | macOS Tahoe | Connecting to a malicious SMB server could crash the system | This was resolved through more careful memory handling. | CVE-2026-39873 |
| SMB | macOS Tahoe | A remote user could crash the system or corrupt kernel memory | More careful memory handling now closes this gap. | CVE-2026-64696 |
| SMB | macOS Tahoe | An app could force the system to crash unexpectedly | A type-confusion flaw was corrected through more careful memory handling. | CVE-2026-64704 |
| Spotlight | macOS Tahoe | An app could gain access to a user's sensitive data | An out-of-bounds read was closed off with stricter bounds checking. | CVE-2026-43774 |
| StorageKit | macOS Tahoe | An app could reach sensitive user data it shouldn't | A race condition was closed off with additional validation checks. | CVE-2026-43770 |
| udf | macOS Tahoe | An app could trigger an unexpected system shutdown | This was corrected with improvements to memory handling. | CVE-2026-43768 |
| WebDAV | macOS Tahoe | An app could trigger a denial-of-service condition | Better memory management now prevents a use-after-free condition that existed here. | CVE-2026-64703 |
| WebDAV | macOS Tahoe | An app could leak kernel memory contents | A memory-initialization flaw was corrected through more careful memory handling. | CVE-2026-64699 |
| WebKit | macOS Tahoe | Loading specially crafted web content could expose process memory contents | This was resolved through more careful memory handling. | CVE-2026-43740 |
| WebKit | macOS Tahoe | A website could tell whether the user had previously visited a given link | More thorough checks now close this gap. | CVE-2026-64713 |
| WebKit | macOS Tahoe | Visiting a site that embeds malicious content in a frame could lead to a spoofed interface | This was resolved with interface improvements. | CVE-2026-64730 |
| WebKit | macOS Tahoe | Specially crafted web content could break out of iframe sandboxing rules | A permissions flaw was fixed through stricter validation. | CVE-2026-64728 |
| WebKit | macOS Tahoe | Loading specially crafted web content could crash Safari unexpectedly | A use-after-free flaw was corrected through improved memory management. | CVE-2026-64783 |
| WebKit | macOS Tahoe | Specially crafted web content could cause Safari to crash without warning | A memory-corruption flaw was corrected through improved state management. | CVE-2026-64757 |
| WebKit | macOS Tahoe | Visiting a website could trigger a denial-of-service condition in the app | This was resolved through better state management. | CVE-2026-43804 |
| WebKit | macOS Tahoe | An app could read files outside the bounds of its sandbox | An access-control gap was closed with stricter access restrictions. | CVE-2026-43821 |
| WebKit Canvas | macOS Tahoe | Loading specially crafted web content could crash Safari unexpectedly | A use-after-free flaw was corrected through improved memory management. | CVE-2026-64718 |
| WebRTC | macOS Tahoe | Specially crafted web content could cause Safari to crash without warning | Out-of-bounds memory access has been prevented with stricter bounds checking. | CVE-2026-64719 |
| Wi-Fi | macOS Tahoe | An attacker in physical proximity could corrupt process memory | More careful memory handling now closes this gap. | CVE-2026-64726 |
| Wi‑Fi | macOS Tahoe | An app could run arbitrary code outside its sandbox or with elevated privileges | A buffer overflow has been closed off with stricter bounds checking. | CVE-2026-43750 |
| xar | macOS Tahoe | An app could trigger a denial-of-service condition | A flaw in the underlying logic was leading to memory corruption, now corrected through better state tracking. | CVE-2026-28932 |
Source 🔗: https://support.apple.com/en-us/128067
More important updates:
CVE-2026-43749
Impact: An issue where directory paths were parsed incorrectly—potentially letting an app escalate to root privileges—was resolved through stronger path validation. The fix is included in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, and macOS Tahoe 26.6
Source 🔗: https://nvd.nist.gov/vuln/detail/CVE-2026-43749
CVE-2026-3784 - libcurl
Impact: Login credentials could be transmitted to a server on a different origin than intended: When making a new CONNECT request through an HTTP proxy, curl would incorrectly reuse an existing connection even if different proxy credentials were being used for the new request. Instead, it should establish or use a distinct connection in that case
Source 🔗: https://nvd.nist.gov/vuln/detail/CVE-2026-3784