WhatsApp Fixed Three Bugs. Meta Says One, CVE-2026-23871, May Have Been Abused With Spam to Leak Your IP Address. Here Is the Version to Be On, per Platform.

Update WhatsApp today, and check the version number rather than trusting the store. On Android, be at or above 2.26.35.74. That one number covers all three flaws Meta disclosed on Friday, November 20, 2026, including CVE-2026-23871, the one Meta says "may have been abused in conjunction with specific spam messages." On iPhone, be at or above 2.26.24.72. On WhatsApp Business for Android, 2.26.23.70. On WhatsApp Business for iOS and WhatsApp for Mac, 2.26.23.72.
Meta's word is "may." Nobody has said it was exploited at scale, and it is not on CISA's or VulnCheck's exploited lists as of tonight. It is still the cheapest fix you will make this week.
Check your version
Menu names move between releases, so look for "Help" and "App info."
- Android: open WhatsApp, tap the three dots, then Settings, Help (or Help and feedback), App info. The version is printed there. To update, open the Play Store, search WhatsApp, tap Update.
- iPhone: open WhatsApp, tap Settings, then Help (or Help and feedback). The version is at the top. To update, open the App Store, tap your profile picture, and pull down to refresh the list of pending updates.
- Mac desktop: in WhatsApp, open Settings, then Help. Update from the Mac App Store or the in-app prompt.
- Windows desktop: not named in the November advisory. Meta's May 2026 advisory fixed a Windows flaw (CVE-2026-23863) in 2.3000.1032164386.258709, so be at or above that.
The minimum versions, per platform
All of these are quoted from Meta's 2026 advisory page and the matching CVE records that Meta filed as the CNA.
- WhatsApp for Android: 2.26.35.74 or later. This covers CVE-2026-102769 (fixed in 2.26.35.74), CVE-2026-44908 (2.26.23.74) and CVE-2026-23871 (2.26.17.4).
- WhatsApp Business for Android: 2.26.23.70 or later. This covers CVE-2026-44908 (2.26.23.70) and CVE-2026-23871 (2.26.17.4). The SQL injection advisory names only WhatsApp for Android, not Business.
- WhatsApp for iOS: 2.26.24.72 or later (CVE-2026-44908).
- WhatsApp Business for iOS: 2.26.23.72 or later (CVE-2026-44908).
- WhatsApp for Mac Desktop: 2.26.23.72 or later (CVE-2026-44908).
The flaw with the scam angle, CVE-2026-23871, is Android only: WhatsApp and WhatsApp Business for Android. iPhone users are not named in it.
One detail worth knowing: the CVE-2026-23871 fix version, 2.26.17.4, is well below the other two. That suggests the fix shipped some time ago and the advisory came later. Meta did not give a ship date, so we are not giving one either. If your phone updates apps automatically, you very likely already have it. Check anyway: auto-update is a setting, and settings drift.
For admins with MDM: what you can and cannot enforce
WhatsApp is a consumer app. It does not carry Microsoft's Intune app SDK, so Intune app protection policies and their "minimum app version" conditional launch setting do not apply to it. Most MDMs cannot simply block an old WhatsApp from opening. What they can do:
- Find the old versions. Intune's Discovered apps report, and the app inventory in Jamf and other MDMs, show installed app versions on corporate-owned and supervised devices. Search for WhatsApp and sort by version. On personally owned devices enrolled with a work profile, you usually see only the work side.
- Force the update on Android Enterprise. If you deploy WhatsApp from managed Google Play, set its update priority to high so it updates without waiting for the device to be idle and charging. Google's Android Management API also has a per-app minimum version setting (minimumVersionCode) that makes the device try to update and reports non-compliance until it does. Note that it takes Google Play's internal version code, not the 2.26.x number shown to users, so read the code off a patched device first.
- Push the update on iOS. For WhatsApp deployed as a managed app through Apple Business Manager, send the app update command from your MDM, or turn on automatic updates for that app if your MDM supports it.
- Tell people. For personal phones, a one-line note with the version number above and the "Help, App info" path is the control you actually have.
We checked these MDM capabilities against our own knowledge of the products, not against a vendor document for this specific app. Confirm the setting names in your console.
What is confirmed
Meta's November 2026 update lists three CVEs. Quoting its advisory and its CVE records:
CVE-2026-23871, scored CVSS 3.1 3.5 (Low) by Meta, CWE-918 (server-side request forgery): "Incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4 could have caused a target's device to reveal its IP information to an attacker if an attacker sent media from an attacker-controlled URL when a crafted Click to WhatsApp ad-reply message was rendered and displayed in a message thread. This issue may have been abused in conjunction with specific spam messages."
In plain terms: Click to WhatsApp ads are the ads on Facebook and Instagram that open a WhatsApp chat with a business. A crafted reply of that type could make your phone fetch media from a server the sender controls, and that fetch hands the sender your IP address. That is what is described: an IP address leak, not a takeover of the phone or the account. An IP address can reveal your rough location and your internet provider, and it tells a scammer that a real person opened the message.
CVE-2026-102769, CVSS 3.1 6.8 (Medium), CWE-89 (SQL injection): a SQL injection "when the recipient tapped on a specially crafted 'order details' message from an unofficial client in WhatsApp for Android prior to version 2.26.35.74 could have allowed deletion of locally-stored WhatsApp files and, only if the user is online at time of receipt, leaked one bit of information asked by the attacker about the user's chat database via an induced-crash delivery receipt timing sidechannel." Meta: "We have not seen evidence of exploitation in the wild." It needs you to tap the message.
CVE-2026-44908, CVSS 3.1 4.8 (Medium), CWE-296 (improper following of a certificate's chain of trust): a flaw in the check WhatsApp uses to trust Meta AI's confidential computing backend (Private Processing). It "could have allowed someone positioned within Meta infrastructure to bypass the hardware root of trust by presenting clients with a VCEK certificate signed by a key other than the hardware manufacturer's." Meta says any such certificate would have had to be published to a third-party transparency ledger, and "the ledger shows that every published VCEK certificate chains to the hardware root of trust, confirming no exploitation." This is about the promise that even Meta cannot read your Private Processing requests. The attacker it describes is an insider at Meta, not a stranger texting you.
What is not known: the scam link
The "used in scams" framing rests on two statements, and both come from Meta:
- The advisory's own sentence: the bug "may have been abused in conjunction with specific spam messages."
- A WhatsApp spokesperson told The Hacker News the bug was found while the company was disrupting a scam campaign, and that a scammer was using it to make scam messages seem more credible.
That is one source: Meta. Meta has not said how many people received those messages, which countries, whether the IP addresses gathered were used for anything further, or what "more credible" meant in practice. It published no sender numbers, domains, server addresses or ad accounts. We are not upgrading "may have been abused" to "exploited," and you should not either.
Not on the exploited lists, as checked tonight:
- CISA KEV: none of the three CVEs is in the catalog, version 2026.11.20, released November 20 at 17:48 UTC, 1,790 entries. The WhatsApp entries it does hold are older: CVE-2019-3568, CVE-2019-18426 and CVE-2025-55177.
- VulnCheck KEV: no entry for any of the three at 23:48 UTC November 20. The same query returned the known CVE-2025-55177 entry, so the zero is a real zero, not a broken query.
- NVD: all three records were published November 20 (16:17 to 17:18 UTC) and read "Received." NVD has not added its own analysis; the scores above are Meta's.
Why a scammer wants your IP address
An IP leak sounds minor, and by score it is. For a scam crew it is useful. It confirms the number belongs to a live person who opened the message, which is what makes a target worth a second message. It gives a rough city, which lets the next message mention it. If you have fallen for one of these, assume the crew knows roughly where you are, and treat any follow-up that seems to know your town as part of the same script.
The everyday defense is the same as it was before this bug. Do not answer investment, job, or "wrong number" chats from strangers. Do not tap ad replies or "order details" from businesses you did not contact. Turn on WhatsApp's "Silence unknown callers" and set "Who can add me to groups" to My contacts, in Settings, Privacy.
Indicators and edge check
None published in the sources we read: no phone numbers, domains, URLs, IP addresses or hashes. We fed nothing to our feed for this story.
We did not run our edge check. Our sensors watch web traffic to our own sites; a bug inside a phone app is invisible to them, and a zero from them would mean nothing.
How we know
We read Meta's WhatsApp security advisories page for 2026 (November Update section) and the three CVE records on the NVD API, all filed by Meta's CVE team as the CNA. The version numbers and descriptions above are quoted from them. We downloaded CISA's KEV JSON (catalog 2026.11.20) and searched it for each CVE and for every WhatsApp and Meta entry. We queried VulnCheck KEV by CVE ID with a control query. The spokesperson's statement comes from The Hacker News; we did not reach Meta ourselves. The MDM section is our own guidance, not Meta's.
What we did not verify: the ship date of the 2.26.17.4 fix; anything about the scam campaign beyond Meta's two statements; and the exact MDM setting names in your console version.
Sources
- Meta, WhatsApp Security Advisories, 2026 Updates, November Update: whatsapp.com/security/advisories/2026
- NVD records: CVE-2026-23871, CVE-2026-102769, CVE-2026-44908
- CISA, Known Exploited Vulnerabilities Catalog, version 2026.11.20
- VulnCheck, VulnCheck KEV, queried November 20, 2026, 23:48 UTC
- The Hacker News, "WhatsApp Patches 3 Security Flaws, Including Android Bug Suspected of Use in Scams," November 20, 2026, with the WhatsApp spokesperson's statement
Read next
The scam this bug was suited to is the one where everyone in the chat but you is fake. We took one apart in OPCOPRO: The Investment Scam Where You're the Only Real Person.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.