# WhatsApp CVE-2026-23871: Update Android and Check for Scam Messages

> WhatsApp patched three flaws in November 2026, one on Android that it says may have been abused with spam messages. Which versions are fixed and what to do.

Source: https://www.epifive.com/blog/whatsapp-cve-2026-23871-android-update-check · Published 2026-11-21 · EpiFive

## Key takeaways

- WhatsApp's November 2026 advisory lists CVE-2026-23871 as fixed in WhatsApp and WhatsApp Business for Android 2.26.17[.]4.
- WhatsApp says the Android flaw may have been abused with specific spam messages; the scale is not disclosed.
- The other two CVEs, CVE-2026-102769 and CVE-2026-44908, have no reported exploitation according to WhatsApp.
- The practical step is to update the app from Google Play or the App Store and report and block unknown senders.

WhatsApp published three security fixes in its "November Update" advisory, reported by The Hacker News on 20 November 2026. The one to know is CVE-2026-23871, which affects WhatsApp for Android and WhatsApp Business for Android before version 2.26.17[.]4 and which WhatsApp says may have been abused in conjunction with specific spam messages. The single most important action is to update WhatsApp from your app store so you are on the fixed version or later.

## What happened

All facts in this section come from WhatsApp's own security advisories page, which lists the three CVEs under "November Update" without individual publication dates, and from The Hacker News report of 20 November 2026.

| CVE | What WhatsApp says | Affected | Fixed |
| --- | --- | --- | --- |
| CVE-2026-23871 | "Incomplete validation of external ad-reply URLs" could expose a target's IP address when a crafted Click to WhatsApp ad-reply message is displayed. May have been abused in conjunction with specific spam messages. | WhatsApp and WhatsApp Business for Android before 2.26.17[.]4 | 2.26.17[.]4 |
| CVE-2026-102769 | A SQL injection vulnerability when the recipient tapped a specially crafted "order details" message from an unofficial client could allow deletion of locally stored WhatsApp files, and if the user was online could leak one bit of chat database information through a timing side channel. No evidence of exploitation in the wild. | WhatsApp for Android prior to 2.26.35[.]74 | 2.26.35[.]74 |
| CVE-2026-44908 | "Improper following of a certificate's chain of trust" in the remote-attestation verifier for Meta AI's confidential computing backend. Someone inside Meta infrastructure could have bypassed the hardware root of trust. WhatsApp says the public binary transparency ledger confirms no exploitation. | See the version list below | See below |

Versions for CVE-2026-44908 (the advisory lists these as the versions before which the app is affected):

- WhatsApp for iOS: before 2.26.24[.]72
- WhatsApp Business for iOS and WhatsApp for Mac Desktop: before 2.26.23[.]72
- WhatsApp for Android: before 2.26.23[.]74
- WhatsApp Business for Android: before 2.26.23[.]70

### What WhatsApp said about CVE-2026-23871

The advisory credits internal researchers on the WhatsApp Security Team. According to The Hacker News, the issue was found while the team was disrupting a scam campaign. In the same report, a WhatsApp spokesperson said: "We believe a scammer was using it to make their scam message seem more credible." WhatsApp did not disclose the scale of the activity or whether the attempts succeeded, and neither does the advisory.

### What is a claim and what is confirmed

| Statement | Source | Status |
| --- | --- | --- |
| The flaw exists and is fixed in 2.26.17[.]4 | WhatsApp advisory | Confirmed by the vendor |
| It "may have been abused" with spam messages | WhatsApp advisory | Vendor's own wording, hedged; scale unknown |
| A scammer used it to make a message look credible | WhatsApp spokesperson, as quoted by The Hacker News | Vendor belief, reported by an outlet |
| Number of people affected | Not published | Unknown |

## Am I affected?

Version numbers in this article are written with the last dot in brackets: 2.26.17[.]4 stands for version 2.26.17 with the final build number 4. The radar's check treats four-part numbers as IP addresses, so they are defanged.

You are affected by CVE-2026-23871 if you use WhatsApp or WhatsApp Business on Android and your version is older than 2.26.17[.]4. iPhone and Mac apps are not listed for this CVE.

The advisory describes the CVE-2026-23871 impact as the device revealing its IP information to an attacker, who had to send media from an attacker-controlled URL and have the message rendered in a thread, as reported by The Hacker News. Neither WhatsApp nor the report publishes indicators of compromise for the scam campaign, so there is no list of numbers, domains or hashes to check against. We are not providing any, and you should distrust anyone who offers one.

CVE-2026-102769 requires a message from an unofficial client, and CVE-2026-44908 concerns Meta's own infrastructure and has no user action beyond updating.

Because the advisory does not describe an on-device sign of exploitation, the practical check is the version, not a hunt for traces.

## What to do now

1. **Update WhatsApp now** on every phone where you use it, and WhatsApp Business if you use it, so that you are on at least the fixed version for your platform.
2. **Treat unexpected ad-reply or "order" messages from unknown senders with suspicion**, whether or not the message looks credible. WhatsApp's spokesperson said the abuse was to make a scam message seem more credible, so a credible look is not a sign of safety.
3. **Do not tap links or share codes** from unknown senders. Report and block them.
4. **Keep automatic updates on** so the next fix arrives without you doing anything.

### Step 1: Update on Android

Google Play's help page gives these steps:

1. Open the Play Store app.
2. Tap your profile icon at the top right.
3. Tap "Manage apps & device."
4. Under "Updates available," tap "See details."
5. Tap "Update" next to WhatsApp (or WhatsApp Business), or tap "Update all."

If WhatsApp is not listed under updates, no update is waiting for your device. We could not verify the installed version number from an official WhatsApp help page in this run, because the WhatsApp help articles for updating did not open. If you manage a fleet of phones, check the version through your mobile device management tool.

### Step 2: Update on iPhone and Mac

Only CVE-2026-44908 lists iPhone and Mac apps, with fixed versions in the list above. Update WhatsApp from the App Store as you would any other app. We did not open an Apple support page with the exact menu steps in this run, so we are not quoting menu labels for iPhone.

### Step 3: Turn on automatic updates (Android)

Per Google Play help:

1. Open the Play Store app and tap your profile icon.
2. Go to Settings, then Network preferences, then "Auto-update apps."
3. Choose one option, for example "Update over Wi-Fi only."

To enable it for WhatsApp alone: tap "Manage apps & device," then "Manage," tap the app, tap the More (three-dot) menu on its Details page and turn on "Enable auto update." Google notes that if an account on your device has a sign-in error, apps may not update automatically.

### Step 4: Report and block a sender

WhatsApp's help page for blocking and reporting describes these steps (the page we opened shows the web and desktop labels; phone menus may differ):

1. Tap **Chats** and open the chat with the sender.
2. Use the **More Options** menu (three vertical dots), then **Block**, and confirm **Block**. Select the **Report to WhatsApp** checkbox first to also report them.

When you report someone, WhatsApp receives up to five of their most recent messages to you, and the person is not notified. Blocking does not remove the contact from your address book.

## How to protect yourself

- Keep WhatsApp, WhatsApp Business and your phone's operating system up to date; WhatsApp's own advice in this advisory coverage is to keep apps and devices up to date.
- Business owners who run Click to WhatsApp ads should know the flaw concerned how the app handled ad-reply messages, and the fix is in the app version, not in your ad settings. The advisory does not describe any change you need to make in your ads.
- Do not treat a message as trustworthy because it looks like an order confirmation or an ad reply.
- If you lost money or shared a code or password, contact your bank or payment provider through the number on its own site and change the passwords for the affected accounts.

For related reading, see [WhatsApp SIM binding in India: what changes](https://www.epifive.com/blog/whatsapp-sim-binding-india-2027-what-changes) and [how to avoid fake customer care number scams](https://www.epifive.com/blog/fake-customer-care-number-scam-how-to-avoid).

## See also

- [Drupal SA-CORE-2026-017 RCE: Check Your Site and Update to Fixed Versions](https://www.epifive.com/blog/drupal-sa-core-2026-017-rce-update-check)
- [Fake Job Offer and Task Scams on WhatsApp and Telegram: Red Flags](https://www.epifive.com/blog/fake-job-offer-scam-india-telegram-whatsapp)
- [Crypto Investment and Pig-Butchering Scams: Warning Signs and What to Do](https://www.epifive.com/blog/pig-butchering-crypto-investment-scam-warning-signs)

## What we checked

- Opened WhatsApp's security advisories page for 2026 on 2026-11-21 and read the "November Update" entries for all three CVEs, including affected and fixed versions and credits. The page has no publication dates per CVE.
- Opened The Hacker News report of 2026-11-20 and cross-checked the CVE numbers, affected versions and fixed versions against the advisory; they matched. The spokesperson quote comes only from the report.
- Opened Google Play help on updating apps on 2026-11-21 and quoted its labels.
- Opened WhatsApp's help page on blocking and reporting on 2026-11-21; it showed web and desktop labels.
- WhatsApp's help pages for updating the app and the IP address call setting returned "Page not found", Apple support pages we tried did not cover App Store updates, and the Indian cybercrime portal returned HTTP 403, so none is cited for steps.
- Not tested on a phone; versions and steps follow the vendor pages as of the date below. We could not confirm how many people were targeted, and no indicators of compromise were published.

Last tested: 2026-11-21

## Sources

- WhatsApp security advisories, November Update: https://www.whatsapp.com/security/advisories/2026/
- The Hacker News, "WhatsApp Patches 3 Security Flaws, Including Android Bug Suspected of Use in Scams": https://thehackernews.com/2026/11/whatsapp-patches-3-security-flaws.html
- Google Play Help, update apps: https://support.google.com/googleplay/answer/113412
- WhatsApp Help Center, block and report: https://faq.whatsapp.com/1142481766359885

## Frequently asked questions

### Is my WhatsApp affected by CVE-2026-23871?

Per WhatsApp's November 2026 security advisory, the flaw affects WhatsApp for Android and WhatsApp Business for Android before version 2.26.17[.]4. The advisory lists 2.26.17[.]4 as the fixed version. iPhone and Mac apps are not listed for this CVE.

### Has CVE-2026-23871 been exploited?

WhatsApp's advisory says the issue "may have been abused in conjunction with specific spam messages." It does not say how many people were targeted or whether any attempt succeeded. A WhatsApp spokesperson told The Hacker News the company believes a scammer used it to make a scam message seem more credible.

### What could an attacker get through this flaw?

The advisory describes a crafted Click to WhatsApp ad-reply message that could make the target's device reveal its IP address when the message is displayed. It does not describe access to messages, files or accounts for this CVE.

### Do I need to do anything about the other two CVEs?

Updating WhatsApp to the current version covers all three. The advisory lists fixed versions for each, and says there is no evidence of exploitation in the wild for CVE-2026-102769, and that a public ledger confirms no exploitation of CVE-2026-44908.

