Updated for January 15, 2026
iOS 26 adoption looks unusually low in January 2026, but a Safari reporting change may be skewing the numbers. Here’s what’s really happening — and why iOS 26.2 security fixes matter.
In the past week, iOS 26 has become a rare kind of Apple story: not a feature leak or a new device rumor, but a full-blown debate about whether millions of iPhone owners are refusing to upgrade — and whether the stats “proving” it are even measuring the right thing.
On one side are widely shared analytics dashboards suggesting iOS 26 is barely installed compared to past releases. On the other is a growing pile of evidence showing those dashboards may be undercounting iOS 26 users because Safari no longer reports iOS versions the way it used to. (Macworld)
But here’s the part that matters more than the numbers: Apple’s latest security notes show iOS updates released in December patched WebKit vulnerabilities tied to “extremely sophisticated” attacks — and if your iPhone can run iOS 26, the fix you need is on iOS 26.2. (Apple Support)
Below is the latest picture as of January 15, 2026: what the adoption data says, why it may be misleading, what’s likely driving upgrade hesitation anyway, and what you should do right now if you care about security.
What sparked the “iOS 26 adoption crisis” story
The controversy began when third‑party web analytics (not Apple’s own reporting) appeared to show iOS 26 usage share far below typical January adoption levels, with iOS 18 still dominating detected iPhone traffic. (AppleInsider)
AppleInsider summarized the StatCounter‑based breakdown that circulated across the Apple news ecosystem:
- ~10.6% on iOS 26.1
- ~4.6% on iOS 26.2
- ~1.1% on iOS 26.0
- ~16.3% total on any iOS 26 version (AppleInsider)
Those figures looked even worse next to historical StatCounter‑style comparisons (over 50% adoption by this point in prior cycles), which helped the narrative explode: iOS 26 must be getting avoided — likely because of the polarizing Liquid Glass redesign and a general sense of update fatigue. (TechRadar)
That’s the headline version.
The reality, as it often is with data stories, is more complicated.
Why the adoption numbers may be wrong: Safari’s “frozen” iOS reporting
Within days, multiple analysts and publications converged on the same culprit: Safari’s user‑agent string.
Macworld laid out the key observation: on iOS 26, Safari continues to send a user‑agent string where the “iPhone OS” portion is stuck on iOS 18.x, even while another part of the string reflects Safari’s newer version. (Macworld)
Macworld’s example compares:
- Safari 18.6 UA snippet:
CPU iPhone OS 18_6 … Version/18.6 … - Safari 26.0 UA snippet:
CPU iPhone OS 18_6 … Version/26.0 …(Macworld)
In other words, if a stats provider is reading the “iPhone OS 18_6” portion to classify the operating system, a huge share of iOS 26 Safari traffic can be miscounted as iOS 18. (Macworld)
Pixel Envy (Nick Heer) went further, arguing that StatCounter’s iOS 26 counts may primarily reflect third‑party browsers (Chrome, Firefox, etc.) that still expose the current iOS version in the user agent — while Safari traffic gets folded into iOS 18. (Pxlnv)
AppleInsider echoed the same conclusion: the adoption story was “sensational” in part because the underlying measurement was flawed — a reminder that third‑party “OS market share” dashboards are only as good as the signals they can reliably detect. (AppleInsider)
So… is iOS 26 adoption actually fine?
Not necessarily “fine,” but almost certainly not as catastrophic as the ~16% headline implied.
Pixel Envy points to TelemetryDeck (in‑app analytics) indicating iOS 26 adoption around ~55% at the time of writing, while also noting that TelemetryDeck’s historical iOS 18 adoption readings were higher than StatCounter’s — meaning neither data source is a perfect mirror of reality. (Pxlnv)
The most grounded takeaway right now is:
- StatCounter-style browser analytics likely undercount iOS 26 because of Safari reporting changes.
- Even after correcting for that, iOS 26 adoption may still be meaningfully slower than recent iOS cycles. (Pxlnv)
Why some iPhone owners are still holding back on iOS 26
Even if the “16%” figure is misleading, it’s clear from coverage and commentary that iOS 26 hasn’t sparked the usual “upgrade immediately” reflex. Here are the most cited (and most plausible) drivers, based on what’s being discussed across the reporting:
1) Liquid Glass is a bigger UI shift than many expected
A dramatic visual overhaul can slow adoption all by itself, especially among users who value familiarity over new features. Liquid Glass has been repeatedly singled out as a potential friction point. (TechRadar)
2) “If it ain’t broke…” — iOS 18 still feels stable
When the current OS is stable and does what people need, upgrades often become a “later” task — especially after a busy holiday season. TechRadar explicitly points to ongoing iOS 18 support reducing perceived urgency. (TechRadar)
3) Features aren’t equally compelling for everyone
Some of iOS 26’s headline capabilities may be more appealing to power users than everyday iPhone owners. If the “wow” factor doesn’t land, the default behavior becomes delay. (TechRadar)
4) Enterprises and cautious users move slower
Even without hard numbers, it’s common for enterprise fleets and risk‑averse users to wait for x.1/x.2 stability and compatibility confirmations — and iOS 26 is now deep enough into its cycle that many are watching for the next maintenance releases before jumping. (9to5Mac)
The security reality check: why iOS 26.2 matters even if you dislike iOS 26
Here’s where the conversation shifts from aesthetics and analytics to something more concrete.
Apple’s security documentation for iOS 26.2 includes WebKit vulnerabilities where Apple says it is aware of reports that the issues “may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26.” (Apple Support)
Apple also documented similar WebKit language in the security notes for iOS 18.7.3 (for devices that cannot install iOS 26), again referencing exploitation in “extremely sophisticated” attacks against iOS versions before iOS 26. (Apple Support)
The key detail most people miss: the “right” update depends on your iPhone model
Apple’s own availability lists make the upgrade path clear:
- iOS 26.2 is available for iPhone 11 and later (Apple Support)
- iOS 18.7.3 is available for iPhone XS / XS Max / XR (and certain iPads) (Apple Support)
So if you’re on an iPhone 11 or newer, the security fixes tied to those WebKit issues are on iOS 26.2, not iOS 18.7.3. (Apple Support)
Security experts are pushing “update + restart” right now
Malwarebytes’ January 13 advisory argues that the December 12 patches addressed WebKit zero‑days linked to spyware campaigns, and that users should update and restart devices, partly because restarts can disrupt some forms of memory‑resident malware. (Malwarebytes)
Even if you assume you’re not a “high‑value target,” the core point remains: WebKit is a massive attack surface because it underpins Safari and web rendering across apps — and once exploits exist, they tend to spread beyond the original targets over time. (Malwarebytes)
What’s next: iOS 26.2.1 is being tested, and iOS 26.3 is coming later this month
While iOS 26 adoption arguments rage on, Apple’s update train keeps moving.
iOS 26.2.1: likely bug fixes and/or security patches
Both MacRumors and 9to5Mac report signs that Apple is testing iOS 26.2.1, with expectations it could arrive soon (potentially before iOS 26.3). (MacRumors)
iOS 26.3: beta features include Android switching tools and EU-only changes
MacRumors’ iOS 26.3 beta roundup highlights:
- A new iPhone‑to‑Android transfer tool for moving photos, messages, notes, apps, and more (MacRumors)
- Notification Forwarding and proximity pairing features in the EU (linked to Digital Markets Act compliance) (MacRumors)
- Preparations for end‑to‑end encrypted RCS support (MacRumors)
- Notes on Apple’s “Background Security Improvement” concept being tested in iOS 26.3 betas (though MacRumors notes the test updates referenced don’t actually contain security fixes yet) (MacRumors)
What you should do today (January 15, 2026)
If you want a simple, practical decision tree:
If you have an iPhone 11 or newer
- Install iOS 26.2 (or newer if available in your region today). Apple’s security notes explicitly reference exploitation of WebKit issues, and iOS 26.2 is the update line for your device class. (Apple Support)
If you have an iPhone XS / XR / XS Max
- Install iOS 18.7.3. That’s the security track for devices not eligible for iOS 26, and it includes WebKit fixes with the same “extremely sophisticated attack” language in Apple’s bulletin. (Apple Support)
If you’re waiting because you hate Liquid Glass
That’s a valid preference — but treat it separately from security. You don’t have to love a redesign to decide that browser-engine zero-day fixes are worth it.
FAQ: quick answers people are asking right now
“Why do some sites think I’m on iOS 18 when I’m on iOS 26?”
Because Safari’s user-agent reporting for “iPhone OS” can remain stuck on an 18.x value even on iOS 26, which can confuse analytics systems that depend on UA parsing. (Macworld)
“Is Apple’s official iOS adoption rate public?”
Apple doesn’t provide a continually updated public adoption dashboard for iOS versions. That’s why so many reports rely on third‑party proxies (web traffic, app analytics, site logs). (AppleInsider)
“Should I wait for iOS 26.2.1 or iOS 26.3 instead?”
If you’re updating primarily for security, the safest approach is usually to install the latest generally available update now — especially when Apple’s security notes reference active exploitation. (Apple Support)
