WhatsApp has patched three security flaws in its November 2026 security update, and one of them is the kind of story that should make every user check their app version today. WhatsApp says it believes that flaw — a bug in how the Android app handles replies to “Click to WhatsApp” ads — may already have been abused alongside spam messages, with a scammer using it to make fraudulent messages look more credible.
The other two flaws are more serious on paper. One is a SQL injection bug that could delete files stored by WhatsApp on Android if the victim tapped a booby-trapped message. The other sits in the infrastructure behind Meta AI’s Private Processing feature and could, in theory, have let someone inside Meta’s own systems bypass a hardware security check. WhatsApp says it has seen no evidence either of those two was ever exploited.
None of this means WhatsApp itself was “hacked” or that your chats were read. But it does mean the fix is already out, the safe versions are public, and updating takes less than a minute. Here is what each flaw actually does, which versions are safe, and how to check yours.
What Happened
WhatsApp published its November 2026 security advisory on November 20, 2026, listing three vulnerabilities with CVE numbers, severity scores, and the app versions that contain the fixes. The Hacker News and SecurityAffairs both reported the disclosure the same day, and WhatsApp confirmed the details to reporters directly.
The headline detail came from a WhatsApp spokesperson, who told The Hacker News that the first flaw was discovered while the company’s security team was disrupting a scam campaign. “We believe a scammer was using it to make their scam message seem more credible,” the spokesperson said. SecurityWeek received the same explanation. WhatsApp did not say how many people were affected, or whether the scam attempts succeeded.
That context matters, because it flips the usual security story on its head. The flaw that was actually used in the real world is the least severe of the three by its official score. The most severe one, by contrast, has no known victims at all. Scammers do not always need a powerful exploit — a message that looks legitimate is often enough.

Flaw 1: The Scam Bug — CVE-2026-23871 (Android Only)
The first flaw, tracked as CVE-2026-23871, affects WhatsApp and WhatsApp Business for Android in versions before 2.26.17.4. Its severity score is 3.5 out of 10, which security researchers rate as low — but it is the one with real-world abuse attached.
The problem was incomplete validation of external media links in replies tied to “Click to WhatsApp” ads — the ads on Facebook and Instagram that open a WhatsApp chat when you tap them. When a crafted ad-reply message was rendered in a chat thread, an attacker who sent media from a server under their own control could cause the victim’s device to reveal its IP address to that server.
An IP address on its own does not hand an attacker your messages or your account. But it does reveal your approximate location and your internet provider, and in the hands of a scammer running a campaign, it helps confirm that a target is real and active. More importantly, the bug appears to have been used to make scam messages render in a way that looked more convincing — the message appeared to come with legitimate-looking media attached, which is exactly the kind of detail that makes a person trust a message they should not.
WhatsApp’s own security team is credited with discovering and reporting this flaw, and it was found during the disruption of an actual scam campaign rather than in a lab test. That is why WhatsApp’s wording is careful but clear: the issue “may have been abused in conjunction with specific spam messages.” The company has not disclosed the scale of the activity, and it has not said whether the scam attempts worked.
This flaw is Android-only. iPhone users are not named in the advisory for CVE-2026-23871 at all.
Flaw 2: The File-Deletion Bug — CVE-2026-102769 (Android Only)
The second flaw is the most severe of the three by its official score — 6.8 out of 10, rated medium — and it is also Android-only. CVE-2026-102769 is a SQL injection vulnerability in WhatsApp for Android before version 2.26.35.74.
Here is how it worked. An attacker would send a specially crafted “order details” message from an unofficial WhatsApp client — not the official app, but a modified or third-party client. If the recipient tapped that message, the flaw could allow deletion of files stored locally by WhatsApp on the device. The advisory limits the possible damage to files stored by WhatsApp itself, not files across the whole phone, but that can still mean photos, videos, and documents inside your chats.
There is a second, stranger detail. The same flaw could leak a tiny amount of information about the victim’s chat database — literally one bit of information — through a timing trick, but only if the user was online at the exact moment the malicious message arrived. WhatsApp describes it as an “induced-crash delivery receipt timing side channel,” which is a complicated way of saying the attacker could measure how long a delivery receipt took and infer one yes-or-no fact about the chat database. One bit is almost nothing on its own, and exploiting it repeatedly would be slow and unreliable.
The important reassurance: WhatsApp says it is not aware of any attacks in the wild exploiting this flaw. An external researcher reported it through Meta’s bug bounty program, which means it was found by a security researcher and fixed before criminals are known to have used it.
Note the interaction requirement. Unlike the first flaw, which could trigger simply by a message being displayed in a thread, this one needed the victim to tap the crafted message — and the message had to come from an unofficial client. That is a narrower attack path, and it is one more reason to be suspicious of odd “order details” messages, especially from numbers you do not recognise.
Flaw 3: The Meta AI Certificate Bug — CVE-2026-44908 (All Platforms)
The third flaw, CVE-2026-44908, is the most technical of the three, and it affects the most platforms: WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac before 2.26.23.72, WhatsApp for Android before 2.26.23.74, and WhatsApp Business for Android before 2.26.23.70. Its severity score is 4.8 out of 10.
It lives not in the app on your phone but in the infrastructure behind Meta AI’s Private Processing — the confidential-computing system WhatsApp uses for AI features such as message summaries. The flaw was in the remote-attestation verifier, the part of the system that checks that the servers processing your data are genuinely the secure hardware they claim to be.
In theory, a bad actor positioned inside Meta’s infrastructure could have presented a certificate signed by the wrong key — a Versioned Chip Endorsement Key (VCEK) certificate not signed by the hardware manufacturer’s key — to bypass the hardware root of trust. In plain terms, the check that says “this server is the real, secure thing” could have been fooled.
In practice, the attack had a major obstacle built in. Any such certificate would first have to be published to a third-party binary transparency ledger used by WhatsApp Private Processing, and WhatsApp says that ledger shows every published VCEK certificate chains properly to the hardware root of trust — in other words, no fake certificate ever appeared, and there is no evidence of exploitation. This flaw was also reported through Meta’s bug bounty program.
For most users, this flaw is the least actionable of the three: you cannot check a transparency ledger yourself, and there is nothing to do beyond updating. But it is a useful reminder that WhatsApp’s AI features depend on a chain of trust that runs from your phone all the way into Meta’s data centres, and that WhatsApp is now disclosing flaws in that chain publicly.
Which Versions Are Safe
The safe versions differ by app and platform, because each flaw was fixed in a different release. The simplest rule is: update to the latest version available in your app store. But if you want to check precisely, these are the minimum fixed versions from WhatsApp’s November advisory:
| App | Minimum safe version |
|---|---|
| WhatsApp for Android | 2.26.35.74 or later |
| WhatsApp Business for Android | 2.26.23.70 or later |
| WhatsApp for iOS | 2.26.24.72 or later |
| WhatsApp Business for iOS | 2.26.23.72 or later |
| WhatsApp for Mac | 2.26.23.72 or later |
For Android users, version 2.26.35.74 covers all three flaws at once, since it is higher than the fix versions for the other two (2.26.17.4 and 2.26.23.74). For iPhone users, only the third flaw applies, and 2.26.24.72 covers it. WhatsApp Business users should check their Business app separately — it has its own version number and its own update, and updating regular WhatsApp does not update Business.
One detail worth knowing: the fix version for the scam bug, 2.26.17.4, is well below the other two fix versions. That suggests the fix itself shipped some time ago and the public advisory came later. WhatsApp has not given a ship date for it, so do not read anything into the gap — just make sure you are on the latest version.
How to Check Your Version and Update
On Android, open WhatsApp, tap the three dots in the top-right corner, then go to Settings, then Help (or Help and feedback), then App info. Your version number is printed there. To update, open the Google Play Store, search for WhatsApp, and tap Update if one is available. Do the same for WhatsApp Business if you use it — check its version separately.
On iPhone, open the App Store, tap your profile picture, and scroll to see pending updates, or search for WhatsApp and check whether it shows Update or Open. There is no in-app version screen on iOS as convenient as Android’s, but the App Store listing shows the current version number.
On Mac, open the App Store, click Updates in the sidebar, and install any WhatsApp update listed there.
A word of caution that applies to every security update: only update from the official app store — Google Play Store or Apple App Store. Do not download WhatsApp from random websites or APK mirrors promising a “fixed” version, and do not trust messages that link to an update. The irony of this particular disclosure is that one of the flaws involved crafted messages with attacker-controlled media links; a fake “update WhatsApp now” message is exactly the kind of thing scammers send after a security story like this one breaks.
What If You Already Got a Suspicious Message?
If you received a strange message recently — especially one tied to an ad, or an “order details” message from an unknown number — updating is still the first step, because the fixes close the holes regardless of what already happened. After that, a few practical checks are worth doing.
Do not tap links or media in messages from numbers you do not recognise, and do not reply to them — replying confirms your number is active. In WhatsApp, you can long-press a suspicious message, tap Report, and block the sender. If a message pretends to be from a bank, a delivery company, or WhatsApp itself, remember that WhatsApp will never ask for your password, verification code, or payment details inside a chat. If you already tapped something suspicious, run your phone’s built-in security scan if it has one, and check that your WhatsApp is on the latest version.
Also worth checking while you are in settings: make sure two-step verification is switched on for your WhatsApp account (Settings, then Account, then Two-step verification). It does not relate to these three flaws directly, but it is the single most effective protection against account theft in general, and a security story is a good moment to switch it on if you have not already.
Why This Disclosure Matters
There are two things worth taking away from this advisory. The first is that the flaw actually used in the real world was the least severe one on paper. Security scores measure technical impact, not how useful a flaw is to a scammer, and a low-severity bug that makes a fake message look real can do more damage than a high-severity bug nobody knows how to use. That is why WhatsApp’s advice is the same for all three flaws — just update — rather than ranking them by score.
The second is that WhatsApp is now disclosing these flaws with unusual openness. The advisory names the CVE numbers, the scores, the exact fixed versions, and even the fact that one flaw may have been abused. That level of detail is what lets users check their own version and decide for themselves, instead of taking a company’s word that everything is fine. It also follows two fixes WhatsApp shipped in May 2026 — one for an Instagram Reels message-handling bug and one for a Windows attachment-spoofing trick — both of which were reported through the bug bounty program with no evidence of exploitation.
The practical takeaway is simple, and it is the same advice WhatsApp itself gives: keep the app updated on every device you use it on, including WhatsApp Business and the Mac app, and treat unexpected messages with suspicion even when they look legitimate.
What Happens Next
There is nothing further to wait for here — the fixes are already released, and the only action is yours. WhatsApp will continue to publish security advisories as new issues are found, and its bug bounty program remains the main route by which outside researchers report flaws. If you have automatic updates switched on, your phone will pick up the fixed version on its own; if not, a manual check today is worth the minute it takes. The next disclosure will come when it comes — the habit that protects you is keeping the app current, not following each advisory.
FAQs
1. What are the three WhatsApp security flaws fixed in November 2026?
WhatsApp fixed three flaws in its November 2026 security advisory: CVE-2026-23871, an Android bug in Click to WhatsApp ad replies that could reveal a user’s IP address; CVE-2026-102769, an Android SQL injection flaw that could delete locally stored WhatsApp files if the victim tapped a crafted “order details” message; and CVE-2026-44908, a certificate-validation flaw in the infrastructure behind Meta AI’s Private Processing. Only the first is believed to have been abused, alongside spam messages.
2. Was my WhatsApp hacked? Were my messages read?
There is no evidence of that. WhatsApp has not reported any account takeovers or message exposure from these flaws. The IP-address flaw could reveal a user’s IP information to an attacker, the file-deletion flaw could delete files stored by WhatsApp on Android, and the certificate flaw could in theory have bypassed a hardware trust check — but WhatsApp says it has seen no evidence the second or third flaws were ever exploited, and the first was used to make scam messages look credible, not to read chats.
3. Which WhatsApp version do I need to be safe?
On Android, WhatsApp version 2.26.35.74 or later covers all three flaws. WhatsApp Business for Android needs 2.26.23.70 or later. On iPhone, WhatsApp 2.26.24.72 or later is the safe version, and WhatsApp Business for iOS and WhatsApp for Mac need 2.26.23.72 or later. The simplest rule is to install the latest version available in your official app store, and to check WhatsApp Business separately if you use it.
4. How do I check my WhatsApp version on Android and iPhone?
On Android, open WhatsApp, tap the three dots, then go to Settings, then Help (or Help and feedback), then App info — your version number is shown there. On iPhone, open the App Store, tap your profile picture, and look for WhatsApp under pending updates, or search for WhatsApp and check the version on its listing. If an update is available, install it from the official store only, never from a link in a message.
5. What should I do if I received a suspicious WhatsApp message?
Update WhatsApp first, then do not tap links or media in the message and do not reply to it. Long-press the message in WhatsApp, tap Report, and block the sender. WhatsApp will never ask for your password, verification code, or payment details in a chat. If you already tapped something suspicious, make sure your app is on the latest version and consider switching on two-step verification under Settings, then Account, then Two-step verification.
Related Guides
Sources: The Hacker News, Nov 20, 2026; SecurityAffairs, Nov 20, 2026; Cyber Security News, Nov 21, 2026.

