Apple Releases OS 26.2.1 for AirTag 2, Extends Certificates on Older Versions
In conjunction with the introduction of the second-generation AirTag (see “New AirTag Offers Expanded Range, Louder Speaker,” 26 January 2026), Apple has released iOS 26.2.1, iPadOS 26.2.1, and watchOS 26.2.1, all of which are necessary updates to support the new AirTags. Those who are buying new AirTags should update right away; my feeling is that everyone else can ignore the updates and pick up the bug fixes with the OS 26.3 updates, which should be out soon. Apple claims there are also bug fixes, but doesn’t deign to clarify what they might be.
More intriguingly, the company also released updates to four older versions of iOS and iPadOS, dating back to iOS 12. The updates include:
- iOS 18.7.4 and iPadOS 18.7.4
- iOS 16.7.13 and iPadOS 16.7.13
- iOS 15.8.6 and iPadOS 15.8.6
- iOS 12.5.8
Usually, when Apple updates much older operating systems, it’s because of a particularly problematic security vulnerability, though even then, the company seldom goes back more than two releases. However, something else is going on this time, as indicated by the security notes, which state that none of the releases have any published CVE entries.
So what is the reason for these older updates? On my iPhone 6s running iOS 15.8.5, the description for the 15.8.6 update reads:
This update provides important bug fixes and is recommended for all users.
Unhelpful, but in the iOS 12.5.8, iOS 15.8.6, and iOS 18.7.4 release notes, Apple says:
This update extends the certificate required by features such as iMessage, FaceTime, and device activation to continue working after January 2027.
However, the iOS 16.7.13 release notes currently repeat what appears on the iPhone 6s:
This update provides important bug fixes and is recommended for all users.
I think the iOS 16.7.13 description is just a mistake on Apple’s part—someone pasted the wrong text into the content management system. My strong suspicion is that these historical releases are merely administrative updates designed to give users of older devices a year before things start breaking in January 2027. It’s too bad Apple isn’t using the more explicit language in its on-device messages, since it would undoubtedly encourage more people to update.
If you have an older device that is maxed out on one of these older versions, I strongly recommend updating sometime in the next year. There’s no reason to do it right away, but don’t put it off too long or you may forget entirely.
I wonder exactly how devices that don’t update will degrade in functionality. Apple identifies iMessage, FaceTime, and device activation, but it seems likely that other Apple-specific services might also be impacted.
Note that there are a handful of iPad/iPad Pro models which have iPadOS 17 as their terminal OS.
Presumably, an iPadOS 17.7.11 release will be coming soon.
iPhone 12 with iOS 18.7.2, & iPad Minis 5, 6, & 7 with iPadOS 18.7.3
18.7.4 does not show as available on any of them, yet.
Edit: Haven’t shown up yet on 27 Jan 26. I’ll check back later today.
28 Jan 26 Still not showing up on ANY of my iDevices.
3 Feb 26 STILL not showing up on ANY of my iDevices.
I got the update notice for iOS 12.5.8 on an old iPhone 5s (no SIM) and, as you mentioned, it is about the certificate. Updating now.
Thanks for the tip. I’m installing 15.8.6 on my iPod Touch now.
I guess no way to get 18.7.4 on iPhone 16 Pro?
I’m guessing the answer is “no”. I have an iPhone 13 mini on 18.7.3 from the beta channel, and there hasn’t been anything related to 18.7.4 (beta or not) on that phone. The only update that appears is iOS 26 when I turn off the beta channel.
So if this update is to add certificates to keep iOS things like Messages and FaceTime working after January 2027…does that put a hard deadline on staying on iOS 18?
Has there been any precedence for that?
Crazy to be limited in this way for a device as new as iPhone 16 Pro.
I’m not sure I understand this statement. Isn’t the purpose of the updates is to extend certain certificates so that they will “continue working after January 2027”? I don’t read that as being older devices only have one year left before they start breaking?
I did notice that there are significant differences in the size of the updates, with the updates for older systems being relatively small. Presumably, the older OSs only received certificate updates, but it is hard to say exactly what is going on with the newer updates. Note that some security issues never get CVE entries, and who knows what minor bugs Apple decides to fix.
To give them a year to update, before it would (otherwise) stop working.
Seems like the same concept to me. In January 2027, the previous certificate will expire so things like iMessage and FaceTime will stop working. Since it’s January 2026, these devices have one year left before they start breaking, if you don’t install these updates.
iOS updates like added AirTag 2nd gen. and fixes (who knows what those are. Nothing about public security fixes in Apple security releases - Apple Support (“This update has no published CVE entries.”). Releases - Apple Developer didn’t even mention any details). Wow, 2 iPhone 6+'s iOS v12.5.7’s software update screens showed “This update extends the certificate required by features such as iMessages, FaceTime, and device activation to continue working after January 2027…” for 89.5 MB v12.5.8. Amazing.
Weird. I just updated two iPhones (13 and 12 mini from v26.2). I didn’t see my apps’ icons on my home screen for like a minute. Same in App Store’s Account list. Did anyone else noticing this too?
Did you guys notice anything different? I never saw that line in my 12 mini before it as shown in my https://matrix.zimage.com/_media_proxy/v1/media/download/AVk3o1uPGMJn-GT9LUxZ1uFgDI2z3aMduUINh5pyXIEco2-kvvkcWgTz9LvvOy45LwIPpqevk7FdQ390Ir-lGfVCecRXLjHwAHJvc3MxNTQubmV0L25tR1F2ZExnQmFyS1ZTWm9ZQkJYT2dQSg screen shot. I assume it is telling user that you can swipe down for its control center.
I have had that line on my 15 for as long as I’ve had it IIRC. I always interpreted it as if saying there’s something you can drag here. Kind of like the home bar at the bottom indicating that’s how you get back to the springboard.
I also see that line on my 13 mini (but not on my updated iPod Touch).
I also assume it’s a hint to swipe-down from there for the Control Center. I noticed that swiping-down from other locations does other things, so it may be a useful reminder for some people.
I never noticed it before on my 13 mini. But I just did a search and I see it in a few screen shots you shared in a post from 2023:
Do You Use It? iPhone Always-On Display Popular but Not Universal - #9 by Simon
Here’s an interesting update. A TidBITS reader from Australia sent me this screenshot, which shows that iOS 16.7.13 also fixes a mobile network issue for iPhone X and iPhone 8 models when establishing a connection to emergency services in Australia.
I don’t see that on my ‘13 Mini. In fact, I was never offered anything beyond 18.7.2…
I’ve been doing some research for Advanced Mobile Location in calling emergency services where I live in the EU. I went back to the Wikipedia page for AML and followed the footnote link to an Australian govt site which tells more about it. Perhaps this 16.7.13 update is related to that.
And now it looks like Apple is revising the legacy updates:
Thanks for that update. I was able to upgrade my iPod Touch to 15.8.6 with no problem, when I did it right after the release.
But when I tried to upgrade my iPad Air 2 to the same version, I got this incredibly misleading error:
Verification failure makes sense if the image is no longer signed, but the bit about not being connected to the Internet is flat-out wrong and incredibly misleading.
I spent over and hour troubleshooting my network connection trying to fix this before giving up last night. Had I known the truth, I would have stopped trying after the first attempt.
Followup. I just tried again (about 4:30 pm, Eastern time, January 28th), and this time verification didn’t fail. The installation is now proceeding. So it looks like they’ve restored the signing at least for 15.8.6 on a non-cellular iPad Air 2.
… And several minutes later, it has rebooted. Presumed successful.
It seems this update has resulted in serious connection issues in Australia for Telstra customers.
ABC ews:
“Some older iPhones, including iPhone 8, 8 Plus and X, are unable to connect to Telstra’s network after a recent Apple update, the telco says.
The nationwide issue affects calls to all numbers, including emergency calls to Triple Zero (000).
Customers are advised to delay software updates on affected devices and find alternative ways to communicate if needed. ”
I ran into the same issue earlier today with an iPhone SE (original model). Tried it now and it updated to 15.8.6 after about five minutes with two reboots so apparently the update is working.
My iPad Pro 13" rev.1 Settings is showing that there is an iOS 16.7.14 available, but when plugged into the Finder, the Finder reports my 16.7.13 is latest?
Hmm, to update or not update… ;~}
Anyone else seeing this?
I’m not running iPadOS 16 on my iPad, so can’t answer your question directly, but if you don’t update sometime this year, several of your Apple apps will stop working next January.
Sorry, I should have dug further on this before posting. What I posted applies to iOS 16.7.13, not 14.
So far the only thing I’ve found is that iOS 16.7.14 addresses an iOS 16.7.13 issue that caused iPhone 8, iPhone 8 Plus, and iPhone X’s in Australia to be unable to connect to emergency services.
I can only guess a similar issue involves iPad Pro 6.7”, iPad Pro, & iPad5 but can’t locate anything definitive yet.
Sound like it would only apply if I had Cell/Data chip…
thanks
Yes, sounded like that to me too, but the WiFi only iPads were included in the update, so must be more to the iPad versions or Apple just overdid things.
It’s strange that Apple omitted iPadOS 17. My 10.5-inch iPad Pro maxed out at 17.7.10 (August 20, 2025) and as of February 24, 2026 still doesn’t show any certificate or iPadOS updates.
@gmg - FYI, I looked into the specific certificates that had expired in 17.7.10, and I summarized the info on another thread.
It’s so new it doesn’t need fixing. Maybe in 5 years.
Maybe. A few of the certs expire next year, and a few more in the following year. I’m not inclined to revisit exactly which ones. I figure if they are important, they’ll get done.