Apple Releases Emergency Fixes for iPhone 17 Charging Failures and M5 Mac Shutdowns in Enterprise Environments

Apple pushed out two minor point releases on Monday, June 1, 2026, targeting specific hardware glitches that affect a small subset of its newest devices. The updates — iOS 26.5.1 for iPhones and macOS Tahoe 26.5.1 for Macs — don't introduce new features or security patches, making them easy to skip for the vast majority of users .

What each update fixes, and who is affected

The release notes for both updates are unusually precise about what hardware and conditions trigger the bugs.

iOS 26.5.1: wired charging failure on iPhone 17 and iPhone Air

This update fixes a bug that can prevent wired charging on iPhone Air and all iPhone 17 models (iPhone 17, 17e, 17 Pro, and 17 Pro Max) when the battery is nearly drained. Apple describes the issue as affecting only a "small number of users" . In practice, that means a nearly dead phone might refuse to accept a wired charge until the battery recovers enough voltage — a potentially frustrating scenario if you're trying to power on from zero percent.

Device exclusivity is key here. Unlike most iOS point releases, iOS 26.5.1 is offered only to the iPhone 17 series and iPhone Air. It is not available for any iPhone 11 through iPhone 16e model, which stay on the earlier iOS 26.5 release . This strongly suggests the charging issue is tied to a hardware-specific change in Apple's newer iPhone line, rather than a broader software regression.

macOS Tahoe 26.5.1: unexpected shutdowns on M5 Macs

This update addresses a bug where Macs with the M5 chip could unexpectedly shut down when using certain content-filtering network extensions. These extensions are typically deployed in enterprise and managed IT environments — schools, corporations, and government agencies that filter web traffic for security and compliance reasons .

For the typical consumer Mac user who doesn't work on a company-managed device with an M5 chip, this bug simply isn't relevant. The update is still marked as "recommended for all macOS Tahoe users" through Software Update, but its sole documented fix is this enterprise- and M5-specific scenario .

Build numbers and download details

Both updates are small delta releases, with no published CVE entries on Apple's security releases page . That means they contain no security patches — only the targeted bug fixes described above.

• iOS 26.5.1 — build 23F81 . The over-the-air download is approximately 400–600 MB, depending on device and prior version .
• macOS Tahoe 26.5.1 — build 25F80 . Apple hasn't published an exact download size, but early reports confirm it's a modest delta .

Both updates were released simultaneously on June 1, 2026, roughly three weeks after the previous 26.5 releases .

Who should install these updates (and who can safely ignore them)

If you own an iPhone 17, iPhone 17e, iPhone 17 Pro, iPhone 17 Pro Max, or iPhone Air, you should install iOS 26.5.1. Even though the charging bug is rare, being unable to charge a dead phone is a high-stakes failure when it does occur. The update is small and carries no other changes, so the risk of side effects is minimal .

If you're on any other iPhone model, you won't be offered the update at all — and that's by design. Your device remains on the stable iOS 26.5 release .

For Mac users, the calculus is different. macOS Tahoe 26.5.1 is available to all Tahoe users, regardless of hardware, but its one documented fix is for M5-based Macs using enterprise content-filtering tools . If your Mac has an Intel, M1, M2, M3, or M4 processor — or if you're on an M5 Mac without managed-network software installed — there is no functional reason to install this update now. That said, Apple's recommendation applies broadly, and installing it won't hurt.

The bigger picture: Apple's increasingly precise point releases

These types of surgically targeted updates are becoming more common in Apple's release strategy. By restricting iOS 26.5.1 to specific iPhone models and limiting macOS 26.5.1's fix to one processor family in enterprise environments, Apple avoids rolling out unnecessary code changes to tens of millions of unaffected devices. It's a practical approach that reduces update fatigue and minimizes the risk of introducing new bugs to stable hardware.