Release roundup
Apple security updates for iOS and iPadOS, macOS and visionOS, October 2026: 119 fixes led by Safari code execution flaws
Apple's October 2026 updates for iOS/iPadOS, macOS and visionOS cover 119 CVEs. Five high-severity WebKit flaws in Safari allow code execution via malicious websites; none is in CISA KEV. Update to iOS/iPadOS 27.2 or 26.7.2, macOS 27.2/26.7.2/15.8.2, Safari 27.2 and visionOS 27.2 first.
The release at a glance
Apple published its October 2026 security updates on 26 October. The release covers 119 CVEs in scope for our readers: 93 affect iOS and iPadOS and 26 affect Safari. Apple rates five as high, nine as medium, and leaves 105 unscored. No CVE in this release is listed in CISA's Known Exploited Vulnerabilities catalogue.
The five high-severity issues are all in Safari and WebKit: four use-after-free and one type confusion flaw can lead to arbitrary code execution when processing maliciously crafted web content. Fixes are available in Safari 27.2, iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2 and iPadOS 27.2, macOS Golden Gate 27.2, and visionOS 27.2. Two of the flaws also have fixes in tvOS 27.2 and watchOS 27.2.
What matters most
Safari and WebKit. CVE-2026-112623, CVE-2026-112626, CVE-2026-112651 and CVE-2026-112655 are use-after-free issues; CVE-2026-112659 is a type confusion issue. All five are rated 8.8 high, with a network attack vector and no privileges required, but user interaction is required. That keeps them below a wormable pre-authentication bar, but they are the first priority because Safari and WebKit are widely deployed. Fixes are in Safari 27.2, iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2 and iPadOS 27.2, macOS Golden Gate 27.2, and visionOS 27.2. CVE-2026-112626 and CVE-2026-112655 also list fixes in tvOS 27.2 and watchOS 27.2.
iOS, iPadOS and macOS image and app handling. The most relevant medium-severity items are CVE-2026-112415, an out-of-bounds write that can allow an app to cause unexpected system termination or corrupt process memory; CVE-2026-112614, an out-of-bounds write when processing a maliciously crafted image that may lead to unexpected app termination; and CVE-2026-113913, an input validation issue that may disclose sensitive information when processing web content. All three are rated 6.5 medium and are fixed in iOS 26.7.2 and iPadOS 26.7.2 and iOS 27.2 and iPadOS 27.2. CVE-2026-112415 and CVE-2026-113913 are fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2 and visionOS 27.2. CVE-2026-112614 is fixed in macOS Golden Gate 27.2 and macOS Tahoe 26.7.2.
Patch in this order
- Patch the WebKit risk first. Apply Safari 27.2, iOS 27.2 or iOS 26.7.2 for iPhone, iPadOS 27.2 or iPadOS 26.7.2 for iPad, macOS Golden Gate 27.2, and visionOS 27.2. These close the five high-severity arbitrary code execution flaws in Safari.
- Patch older macOS branches. For Macs that cannot move to macOS Golden Gate 27.2, apply macOS Tahoe 26.7.2 or macOS Sequoia 15.8.2 as appropriate to close the image-processing and input-validation issues.
- Update Apple TV and Apple Watch to tvOS 27.2 and watchOS 27.2 where those devices are in scope, to cover CVE-2026-112626 and CVE-2026-112655.
- Then complete the remaining Apple updates. The release covers 93 iOS and iPadOS CVEs and 26 Safari CVEs; most are unscored and none has a CISA KEV due date, so apply the standard update cycle and verify the versions.
Beyond the patch
Next month, the same dynamic will repeat: a large batch of memory-safety fixes across Apple's platforms, most unscored and none on CISA KEV. The management task is to know which devices are behind and to apply the update before the next release changes the baseline. Managed Detection & Response (MDR) fits the WebKit code-execution class because if malicious content is opened, EDR and SIEM see the follow-on activity. Supply Chain Defense & Third-Party Risk fits the patch-cycle problem: Apple is a vendor whose release cadence sets your exposure window.
Every CVE in this release
| CVE | Product | Severity | |
|---|---|---|---|
| CVE-2026-112623 | Safari | High 8.8 | |
| CVE-2026-112626 | Safari | High 8.8 | |
| CVE-2026-112651 | Safari | High 8.8 | |
| CVE-2026-112655 | Safari | High 8.8 | |
| CVE-2026-112659 | Safari | High 8.8 | |
| CVE-2026-112415 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-112614 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-112629 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-112633 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-112634 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-112646 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-113913 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-86971 | iOS and iPadOS | Medium 6.5 | |
| CVE-2026-113907 | iOS and iPadOS | Medium 6.1 | |
| CVE-2026-112413 | iOS and iPadOS | Not scored | |
| CVE-2026-112414 | iOS and iPadOS | Not scored | |
| CVE-2026-112416 | iOS and iPadOS | Not scored | |
| CVE-2026-112423 | iOS and iPadOS | Not scored | |
| CVE-2026-112425 | iOS and iPadOS | Not scored | |
| CVE-2026-112449 | iOS and iPadOS | Not scored | |
| CVE-2026-112455 | iOS and iPadOS | Not scored | |
| CVE-2026-112456 | iOS and iPadOS | Not scored | |
| CVE-2026-112461 | iOS and iPadOS | Not scored | |
| CVE-2026-112464 | iOS and iPadOS | Not scored | |
| CVE-2026-112466 | iOS and iPadOS | Not scored | |
| CVE-2026-112468 | iOS and iPadOS | Not scored | |
| CVE-2026-112469 | iOS and iPadOS | Not scored | |
| CVE-2026-112470 | iOS and iPadOS | Not scored | |
| CVE-2026-112476 | iOS and iPadOS | Not scored | |
| CVE-2026-112477 | iOS and iPadOS | Not scored | |
| CVE-2026-112479 | iOS and iPadOS | Not scored | |
| CVE-2026-112486 | iOS and iPadOS | Not scored | |
| CVE-2026-112488 | iOS and iPadOS | Not scored | |
| CVE-2026-112491 | iOS and iPadOS | Not scored | |
| CVE-2026-112501 | iOS and iPadOS | Not scored | |
| CVE-2026-112514 | iOS and iPadOS | Not scored | |
| CVE-2026-112515 | iOS and iPadOS | Not scored | |
| CVE-2026-112516 | iOS and iPadOS | Not scored | |
| CVE-2026-112517 | iOS and iPadOS | Not scored | |
| CVE-2026-112522 | iOS and iPadOS | Not scored |
Show all 119
| CVE | Product | Severity | |
|---|---|---|---|
| CVE-2026-112546 | iOS and iPadOS | Not scored | |
| CVE-2026-112554 | iOS and iPadOS | Not scored | |
| CVE-2026-112559 | iOS and iPadOS | Not scored | |
| CVE-2026-112560 | iOS and iPadOS | Not scored | |
| CVE-2026-112561 | iOS and iPadOS | Not scored | |
| CVE-2026-112566 | iOS and iPadOS | Not scored | |
| CVE-2026-112571 | iOS and iPadOS | Not scored | |
| CVE-2026-112576 | iOS and iPadOS | Not scored | |
| CVE-2026-112606 | iOS and iPadOS | Not scored | |
| CVE-2026-112610 | iOS and iPadOS | Not scored | |
| CVE-2026-112611 | iOS and iPadOS | Not scored | |
| CVE-2026-112612 | iOS and iPadOS | Not scored | |
| CVE-2026-112615 | Safari | Not scored | |
| CVE-2026-112621 | Safari | Not scored | |
| CVE-2026-112622 | iOS and iPadOS | Not scored | |
| CVE-2026-112624 | iOS and iPadOS | Not scored | |
| CVE-2026-112625 | iOS and iPadOS | Not scored | |
| CVE-2026-112627 | iOS and iPadOS | Not scored | |
| CVE-2026-112628 | iOS and iPadOS | Not scored | |
| CVE-2026-112630 | iOS and iPadOS | Not scored | |
| CVE-2026-112632 | iOS and iPadOS | Not scored | |
| CVE-2026-112638 | iOS and iPadOS | Not scored | |
| CVE-2026-112639 | Safari | Not scored | |
| CVE-2026-112640 | Safari | Not scored | |
| CVE-2026-112642 | iOS and iPadOS | Not scored | |
| CVE-2026-112652 | iOS and iPadOS | Not scored | |
| CVE-2026-112653 | Safari | Not scored | |
| CVE-2026-112654 | Safari | Not scored | |
| CVE-2026-112656 | iOS and iPadOS | Not scored | |
| CVE-2026-112660 | iOS and iPadOS | Not scored | |
| CVE-2026-112665 | iOS and iPadOS | Not scored | |
| CVE-2026-112671 | iOS and iPadOS | Not scored | |
| CVE-2026-112673 | Safari | Not scored | |
| CVE-2026-112676 | iOS and iPadOS | Not scored | |
| CVE-2026-112678 | iOS and iPadOS | Not scored | |
| CVE-2026-112680 | Safari | Not scored | |
| CVE-2026-112681 | iOS and iPadOS | Not scored | |
| CVE-2026-112682 | iOS and iPadOS | Not scored | |
| CVE-2026-112683 | iOS and iPadOS | Not scored | |
| CVE-2026-112684 | Safari | Not scored | |
| CVE-2026-112686 | Safari | Not scored | |
| CVE-2026-112689 | iOS and iPadOS | Not scored | |
| CVE-2026-112690 | iOS and iPadOS | Not scored | |
| CVE-2026-112691 | iOS and iPadOS | Not scored | |
| CVE-2026-112693 | Safari | Not scored | |
| CVE-2026-112695 | Safari | Not scored | |
| CVE-2026-112697 | Safari | Not scored | |
| CVE-2026-112698 | iOS and iPadOS | Not scored | |
| CVE-2026-112699 | Safari | Not scored | |
| CVE-2026-112701 | iOS and iPadOS | Not scored | |
| CVE-2026-112705 | iOS and iPadOS | Not scored | |
| CVE-2026-112706 | iOS and iPadOS | Not scored | |
| CVE-2026-112707 | iOS and iPadOS | Not scored | |
| CVE-2026-113896 | iOS and iPadOS | Not scored | |
| CVE-2026-113898 | iOS and iPadOS | Not scored | |
| CVE-2026-113904 | Safari | Not scored | |
| CVE-2026-113906 | iOS and iPadOS | Not scored | |
| CVE-2026-113909 | iOS and iPadOS | Not scored | |
| CVE-2026-113910 | iOS and iPadOS | Not scored | |
| CVE-2026-113914 | iOS and iPadOS | Not scored | |
| CVE-2026-113915 | iOS and iPadOS | Not scored | |
| CVE-2026-113949 | Safari | Not scored | |
| CVE-2026-113952 | Safari | Not scored | |
| CVE-2026-65350 | iOS and iPadOS | Not scored | |
| CVE-2026-65385 | iOS and iPadOS | Not scored | |
| CVE-2026-65397 | iOS and iPadOS | Not scored | |
| CVE-2026-84493 | iOS and iPadOS | Not scored | |
| CVE-2026-84495 | iOS and iPadOS | Not scored | |
| CVE-2026-84605 | iOS and iPadOS | Not scored | |
| CVE-2026-86969 | iOS and iPadOS | Not scored | |
| CVE-2026-86970 | iOS and iPadOS | Not scored | |
| CVE-2026-86972 | iOS and iPadOS | Not scored | |
| CVE-2026-86973 | Safari | Not scored | |
| CVE-2026-86974 | Safari | Not scored | |
| CVE-2026-86985 | Safari | Not scored | |
| CVE-2026-86986 | Safari | Not scored | |
| CVE-2026-86989 | iOS and iPadOS | Not scored | |
| CVE-2026-86991 | iOS and iPadOS | Not scored | |
| CVE-2026-86992 | iOS and iPadOS | Not scored |
References
Vendor advisory
Other
CVE
- CVE-2026-112623 — cve.org
- CVE-2026-112623 — NVD
- EUVD-2026-110350 — ENISA EUVD
- CVE-2026-112626 — cve.org
- CVE-2026-112626 — NVD
- EUVD-2026-110177 — ENISA EUVD
- CVE-2026-112651 — cve.org
- CVE-2026-112651 — NVD
- EUVD-2026-110172 — ENISA EUVD
- CVE-2026-112655 — cve.org
- CVE-2026-112655 — NVD
- EUVD-2026-110219 — ENISA EUVD
- CVE-2026-112659 — cve.org
- CVE-2026-112659 — NVD
- EUVD-2026-110202 — ENISA EUVD
- CVE-2026-112415 — cve.org
- CVE-2026-112415 — NVD
- EUVD-2026-110238 — ENISA EUVD
- CVE-2026-112614 — cve.org
- CVE-2026-112614 — NVD
- EUVD-2026-110229 — ENISA EUVD
- CVE-2026-112629 — cve.org
- CVE-2026-112629 — NVD
- EUVD-2026-110261 — ENISA EUVD
- CVE-2026-112633 — cve.org
- CVE-2026-112633 — NVD
- EUVD-2026-110253 — ENISA EUVD
- CVE-2026-112634 — cve.org
- CVE-2026-112634 — NVD
- EUVD-2026-110212 — ENISA EUVD
- CVE-2026-112646 — cve.org
- CVE-2026-112646 — NVD
- EUVD-2026-110142 — ENISA EUVD
- CVE-2026-113913 — cve.org
- CVE-2026-113913 — NVD
- EUVD-2026-110200 — ENISA EUVD