When Your Phone Stops Getting Security Updates
Nothing announces it. The phone still turns on, the apps still open, the camera is still fine. Then one morning your banking app says your operating system is no longer supported, or a browser page warns that the connection cannot be...

Nothing announces it. The phone still turns on, the apps still open, the camera is still fine. Then one morning your banking app says your operating system is no longer supported, or a browser page warns that the connection cannot be verified, and you find out that the last security patch your phone received was eighteen months ago.
This is the most common privacy problem I get asked about, and it almost never arrives as a security question. People ask whether they have to buy a new phone. The honest answer is more interesting than yes or no, and it depends on what you use the phone for rather than on how old it is.
How long support actually lasts
Two numbers matter and they are different. Operating system updates bring new features and new version numbers. Security updates patch holes. A phone can stop getting the first while still getting the second for a year or two, and the second is the one that affects you.
The other thing people get wrong: the clock starts when the model launched, not when you bought it. A handset released in March 2022 and sold at a discount in late 2024 arrives with most of its support window already spent.
| Maker or tier | Security patches promised | Counted from |
|---|---|---|
| Apple iPhone | No published promise, in practice 6 to 8 years | Model release |
| Google Pixel 8 and later | 7 years | Model release |
| Google Pixel 6 and 7 | 5 years | Model release |
| Samsung Galaxy S and Z flagships since 2024 | 7 years | Model release |
| Samsung mid range A series | 4 to 6 years depending on model | Model release |
| Budget Android under about $200 | 2 years, sometimes quarterly rather than monthly | Model release |
Those are the published commitments as of late 2026, and they have improved a lot. A phone bought in 2019 was typically promised three years. The same money today buys five to seven, which quietly changes the cost per year of a more expensive handset.
To find your own date, open the phone settings and look for the security patch level. Android shows it under About phone, usually as a date like 5 September 2026. If that date is more than four months old on a device still within its window, the maker is shipping patches on a slow quarterly cycle rather than monthly. If it is more than a year old, the window has closed.
What stops being safe first
An unsupported phone does not become dangerous all at once. Different layers rot at different speeds, and knowing the order is what lets you make a sensible decision.
The browser usually keeps going longest on Android, because Chrome and the system WebView update through the Play Store rather than through the operating system. That matters more than it sounds, since the browser is where most attacks would arrive. Google has kept Chrome updates flowing to fairly old Android versions, though each year another one drops off the list.
Certificate trust is the one that bites without warning. Root certificates expire on fixed dates and the list lives in the operating system. When one expires and no update replaces it, perfectly ordinary websites start failing with errors that look like your network is broken. This happened at scale in September 2021 when an older root certificate expired and devices on Android 7.1 and below lost access to a large slice of the web overnight. Nothing was attacking those phones. They simply could not be told what to trust any more.
App support goes next, and banks lead the way. Most major banking apps now require Android 10 or newer, or iOS 16 and up, and they enforce it by refusing to launch rather than by warning you. Payment apps and authenticator apps follow the same pattern, which creates the specific trap of an authenticator you can no longer open on a phone you can no longer update.
Kernel and driver flaws are last in visibility and first in severity. These are the ones a patch would have fixed and nothing else will. Exploiting them generally requires you to do something: open a crafted file, install something from outside the store, join a hostile network. Which brings me to the part where I disagree with the usual advice.
Why the advice to replace it immediately is wrong
Search for this problem and you will be told that an unsupported phone is unsafe, full stop, and should be replaced today. I think that framing is both overstated and quietly useful to people selling phones.
Look at how ordinary accounts actually get compromised. Phishing, reused passwords, SIM swaps, and social engineering account for the overwhelming majority of real cases I read about. Remote exploitation of an unpatched consumer phone, with no interaction from the owner, is the domain of commercial spyware vendors and their clients, and their targets are journalists, activists and officials rather than someone whose Galaxy A52 stopped getting patches.
That is not a reason to be relaxed about it. It is a reason to be precise. The risk is not a cliff on the day support ends, it is a slope, and the slope gets steeper the more sensitive the thing you do on the device. A phone that holds your bank, your email recovery address and your authenticator codes has no business running unpatched firmware. The same phone used as a music player, a camera, a sat nav and a kitchen timer is a reasonable thing to keep for another two years.
The custom firmware answer deserves the same scepticism. Installing a community build does bring the Android layer up to date and the volunteers behind these projects do real work. What it generally cannot update is the vendor firmware underneath: the modem, the bootloader, the low level drivers. Those blobs stay at whatever version the manufacturer last shipped, and a fair share of the serious patches each month live down there. A community build is a genuine improvement for a technically comfortable owner and it is not the same thing as a supported device.
Demoting a phone rather than retiring it
Find your patch date and write it down. Settings, then About phone, then Android version on most devices, or Settings and General on an iPhone where the version number tells you most of what you need. If it has stopped moving for more than six months, treat the window as closed.
Move the keys off first. Authenticator codes are the urgent part, because losing access to them is worse than any realistic attack. Export or re enrol them on a supported device before you change anything else. The same applies to passkeys and saved payment cards.
Decide what the phone is allowed to hold. Mine is simple: no banking, no primary email, no password manager, no authenticator, no work accounts. Photos and music are fine. That list takes twenty minutes to enforce and removes most of what an attacker would want.
Turn off automatic Wi-Fi joining and forget saved public networks. An unpatched device on an unknown network is the one scenario where the theoretical risk becomes practical. If the phone still travels with you, the privacy habits in the devices section apply with more force than usual, not less.
Keep the browser updated even though the system is not. On Android, open the Play Store and update Chrome and Android System WebView by hand. Both can be months behind if automatic updates were switched off at some point.
Review permissions once, properly. Old devices accumulate app permissions from apps you stopped using in 2021. The same walkthrough as the iPhone privacy settings worth changing works as a checklist on Android with different menu names.
When the phone finally leaves your hands, the reset matters more than it did when the device was supported, because an unpatched phone is easier to pull data from. Our guide to wiping a phone before selling it covers the order, and the anti theft lock step is the one people skip.
FAQ
How do I check when my phone stops getting updates?
Apple and Google publish supported device lists, and Samsung publishes a per model schedule. Search for your exact model number rather than the marketing name, since regional variants sometimes differ. Failing that, the security patch level date in your settings tells you whether anything has arrived recently.
Does a VPN protect an unsupported phone?
Partly, and not in the way people hope. It encrypts traffic across the local network, so a hostile Wi-Fi access point learns much less. It does nothing about an unpatched flaw in the browser, the image decoder or the operating system itself. Useful as one layer, no substitute for a patch.
Is an old iPhone safer than an old Android?
Usually, for two reasons rather than one. Apple supports models for longer, and it has pushed security fixes to older versions after feature updates stopped. Against that, Android's browser updates arrive through the app store, which keeps the most exposed component current for longer. Neither arrangement makes an unpatched device supported.
Should I keep using an unsupported tablet for banking?
No, and tablets are worse than phones here because they get kept far longer and often sit on a shared home network. If a bank app still launches on a tablet that stopped getting patches three years ago, that is the app's leniency rather than evidence the device is fine.
More in Devices
Devices
Should You Cover Your Laptop Webcam and What Else to Do
You notice the little lens above your screen during a late night of work and wonder whether anyone could be looking back.
Devices
Is a Public Charging Station Safe to Use for Your Phone
Your phone is at 6 percent, your flight boards in 40 minutes, and the only free outlet near the gate is a public charging...
Devices
Smart Speaker Privacy Settings Worth Changing Today
A smart speaker on your kitchen counter hears every conversation in the room, and most people have never opened the settings...