Apple released security updates for iPhones, iPads, and Macs in versions including iOS 18.6.2, iPadOS 18.6.2, iPadOS 17.7.10, macOS Sequoia 15.6.1, Sonoma 14.7.8, and Ventura 13.7.8. The updates address a single serious vulnerability that can cause memory corruption when processing a malicious image file. The issue is an out-of-bounds write and was fixed with improved bounds checking. Apple stated that the flaw may have been exploited in the wild in an extremely sophisticated attack against specific targeted individuals. Users should install the updates immediately by using Software Update on iPhone, iPad, or Mac.
I know you're probably tired of constantly updating your iPhone, iPad, or Mac to fix one issue or another. But there's yet another update that you'll definitely want to install. And hopefully this will be the last one before iOS 26 and the other new OS versions debut next month. Also: Changing these iOS 18 settings significantly improved my iPhone's battery life Last Wednesday, Apple rolled out updates for a slew of products and versions to resolve a security issue. Affecting iPhones, iPads, and Macs, the updates include iOS 18.6.2, iPadOS 18.6.2, iPadOS 17.7.10, MacOS Sequoia 15.6.1, MacOS Sonoma 14.7.8, and MacOS Ventura 13.7.8.
How to update your Apple device - and why If you want to cut to the chase and quickly update your device, here's how. On your iPhone or iPad, go to Settings, select General, and tap Software Update. On your Mac, head to System Settings, select General, and click Software Update. On all platforms, allow the latest update to download and install. Also: How to clear your iPhone cache (and why you should do it before the iOS 26 update) So what do yesterday's updates carry, and why should you install them ASAP? They fix only one flaw, but it's a serious one.
On its pages for and , Apple described the vulnerability as one that affects its and that "processing a malicious image file may result in memory corruption." The company added that it's aware of reports that this flaw may have been exploited in the wild in "an extremely sophisticated attack against specific targeted individuals." Identified as an "out-of-bounds write issue," the problem was fixed through "improved bounds checking."
Collection
[
|
...
]