When a device ages off Apple’s current iOS, iPadOS or macOS branch, it does not necessarily stop receiving updates. Apple’s own security index shows a second kind of update, security-only, that keeps arriving on a fixed list of older devices and versions without ever bringing a new feature.
The two kinds of update look similar in name, a version number and a date, but they carry very different content. Apple has not published a single page explaining the difference; it is visible only by comparing what each branch’s entries actually contain.
Key facts
| Question | Current branch | Security-only branch |
|---|---|---|
| Gets new OS features | Yes | No |
| Gets security fixes | Yes | Yes |
| Major version number changes | Yes, with each cycle | No, stays on the same major version |
| Example, this week | iOS 26.6.2 / iPadOS 26.6.2 | iOS 18.7.10 / iPadOS 18.7.10 |
| Example device list | iPhone 11 and later, named iPad generations | iPhone XS, XS Max, XR, iPad 7th generation |
What it still gets
On macOS, Safari fixes still ship to macOS Sonoma and macOS Sequoia, two versions behind the current macOS Tahoe, on close to the same schedule as fixes for the current release. On the older iOS branch, the same idea holds: Apple’s most recent release for the four devices still on it covers a wide spread of underlying components, not just one or two, months after those devices stopped receiving new iOS version numbers. In both cases the fixing work is real and ongoing; it simply travels under an older name.
Don’t miss the best of The Mac Observer
Set us as a preferred source and our Apple reporting ranks higher in your Google Search results and Discover feed — one tap, no account changes.
What it does not get
None of that work changes the version number. A device on iOS 18.7.10 stays on iOS 18.7.x; it does not gain any part of iOS 26 or the iOS 27 features arriving on the current branch this coming Monday. It does not gain Apple Intelligence capability, new apps, or interface changes of any kind. Apple’s own vintage and obsolete definitions, which govern hardware service and parts rather than software, do not change either way: a device already on the vintage list stays vintage whether or not it keeps receiving security fixes, and a device that is not on that list does not become vintage sooner because it moved to a security-only software branch. None of it applies to devices announced at Apple’s September event either; iPhone 18 Pro, iPhone Duo and AirPods 5 all ship on the current branch, where the distinction between the two kinds of update does not yet come up.
The two kinds of update, in practice
| Gets it | Does not get it |
|---|---|
| Fixes for disclosed security issues | New features tied to the current major release |
| Continued entries on Apple’s security index | A new major version number |
| Shared-component fixes such as WebKit and Safari | Apple Intelligence or other AI-tied capability |
| Coverage alongside the current branch’s own cycle | Any change to vintage or obsolete hardware status |
How long a branch keeps receiving anything
Apple’s index shows the iOS 18.7.x branch and the macOS Sonoma and Sequoia branches all still receiving entries as recently as August 2026, months after the current branch moved well past them. Apple has not published a schedule for how many more point releases any of these branches will get, or a date on which the entries stop appearing. The pattern only tells you what has happened so far, not what happens next.
What Apple has not said
Apple has not published a feature roadmap for any security-only branch, has not stated a point at which security-only updates themselves stop, and has not compared the severity or scope of fixes between a security-only branch and the current one. Everything above describes what Apple’s published entries contain, not what Apple intends going forward.
As of Saturday, September 12, 2026, the most recent security-only entries for both iOS and macOS date to mid-August. Anyone relying on a device in this state should check Apple’s index directly at support.apple.com/en-us/100100 for the current entry rather than assume a fixed timetable, because Apple has not published one.
