Let me tell you something that’s been gnawing at me for weeks: Google’s latest security patch for its Pixel phones feels less like an update and more like a calculated snub. The August 2026 patch, which includes a critical fix for a privilege escalation vulnerability in video processing hardware, was delivered exclusively to the Pixel 8 and newer models. The Pixel 6, 6 Pro, 6a, 7, 7 Pro, and 7a—devices that still technically qualify for five years of support—were left hanging. This isn’t just a technical oversight; it’s a glaring example of how tech giants prioritize novelty over loyalty, and it raises some uncomfortable questions about the ethics of software maintenance in the modern age.
What makes this particularly fascinating is the pattern. Google skipped the February and May updates for the same set of devices last year, only to deliver fixes in June and July. There’s no discernible logic here. If I were a Pixel 6 owner, I’d be tempted to ask: Why should I trust a company that treats my device like a second-class citizen once it’s no longer the flagship? It’s not just about the missing patch—it’s about the message it sends. When a company with Google’s resources and reputation starts cherry-picking which devices get security updates, it erodes the very foundation of consumer trust.
Let’s break down the security implications. The CVE-2026-0163 flaw is rated 'high' severity because it allows malicious software to escalate privileges within the video processing unit. This isn’t just a minor glitch; it’s a potential backdoor for attackers to exploit hardware-level vulnerabilities. And here’s the kicker: the Pixel 6 and 7 series are still running Android 17, which should theoretically include these fixes. But Google’s patching strategy seems to have shifted. Instead of rolling out updates through the Android Security Bulletin, which should be universal, they’re now funneling critical fixes only to newer models. That’s a dangerous precedent. If I were a cybersecurity professional, I’d be advising clients to avoid these older Pixels for sensitive work until they’re patched. But how many users even realize this is happening?
Google’s official stance is that all supported devices receive updates through 'Pixel patches, Google Play system updates, and fixes from the Android Security Bulletin.' But here’s what many people don’t realize: the Android Security Bulletin is a public document, and its updates should apply to all devices. By withholding specific fixes like CVE-2026-0163 from older models, Google is effectively creating a two-tiered security ecosystem. This isn’t just poor planning—it’s a strategic decision to push users toward newer hardware. If you take a step back and think about it, this mirrors the tactics of other tech companies. Apple, for instance, has long been criticized for limiting iOS updates to newer models, but at least they’re transparent about it. Google’s approach feels more insidious because it’s wrapped in the language of 'support windows' and 'security patches,' making it easier to dismiss as a technicality rather than a deliberate business move.
Now, let’s talk about the timeline. The Pixel 6 and 6 Pro are due to reach the end of their five-year support window in October 2026. The Pixel 7 series will linger until 2027 or 2028. But here’s the catch: even if these devices survive until their official cutoff, they’re already being left behind in the security race. This raises a deeper question: What does it mean to have 'five years of support' when the updates don’t actually arrive on time? A detail that I find especially interesting is that Google’s own support page still lists these devices as supported, yet they’re excluded from the latest patch. That’s not just confusing—it’s misleading. If I were a consumer, I’d be furious at being sold a phone with a five-year support promise that’s already failing to deliver on its most basic obligation: keeping me safe.
What this really suggests is that the concept of 'software longevity' is becoming a myth. In the past, companies like Microsoft and Apple promised long-term support for their operating systems, but those promises were often honored. Today, even the most reputable brands are adopting a 'patch what we want, when we want' approach. This isn’t just about security—it’s about control. By withholding updates, companies can nudge users toward newer hardware, driving sales and maintaining market dominance. But at what cost? For users who rely on older devices for work or daily life, this creates a precarious situation. They’re stuck with hardware that’s no longer receiving the fixes they need, yet they’re still expected to pay for software updates that don’t arrive.
Looking ahead, I suspect this trend will only accelerate. As AI and machine learning become more integrated into mobile devices, the pressure to keep hardware up-to-date will increase. Older devices, even if they’re technically supported, will struggle to keep pace with the computational demands of new features. This could lead to a future where 'supported' devices are functionally obsolete before their support window expires. And if you think about it, that’s the ultimate goal of planned obsolescence: not just to make old devices break, but to make them irrelevant through software exclusion.
So what can users do? For now, the advice is simple: keep Google Play system updates current and hope for the best. But that’s not a solution—it’s a temporary bandage. If you’re using a Pixel 6 or 7, you should be asking yourself whether the security risks are worth the cost of upgrading. And if you’re a tech company reading this, I have one message: Stop treating your customers like they’re disposable. Software updates aren’t just technical necessities—they’re the foundation of trust. When you skip a patch, you’re not just leaving a vulnerability open; you’re leaving your users vulnerable.
