A bug in WhatsApp's Click to WhatsApp ad-reply feature could have let an attacker learn a recipient's IP address, and the company's security team found it while disrupting a live scam campaign. WhatsApp fixed the flaw, tracked as CVE-2026-23871, in its November security advisory, with fixes reported on November 20, 2026. According to Security Affairs, a scammer may have used the bug to make fraudulent messages look more legitimate.
What WhatsApp fixed in its November advisory
The advisory covers three flaws, and CVE-2026-23871 is the headline. It affects WhatsApp and WhatsApp Business for Android before version 2.26.17.4, according to CyberUpdates365 and Security Affairs.
The other two fixes are CVE-2026-102769, a SQL injection flaw in WhatsApp for Android that could allow local file deletion and a narrow information leak, and CVE-2026-44908, a certificate-trust weakness in Meta AI Private Processing. CVE-2026-44908 is the only fix with builds listed for iOS and Mac.
How the ad-reply flaw exposed IP addresses
The bug sits in how the app handled external media URLs attached to Click to WhatsApp ad replies. Those URLs were not properly validated. A crafted ad reply could cause a recipient's device to reveal its IP address to the attacker, according to Mallory.
An IP address alone does not hand over a WhatsApp account. The reporting says the flaw did not enable direct account takeover. Its real value to a scammer was credibility. A message that arrives inside a familiar app, tied to an ad that appears to load normally, is easier to trust than a cold text from an unknown number.
That trade-off is the core of the story. Scammers gain a more convincing hook, and users on older builds carry the risk until they update. Businesses that rely on ad-to-chat flows also have a stake, because their customers' trust in those messages is exactly what the flaw could exploit.
Why WhatsApp says the bug matters less than the scam itself
WhatsApp's security team believes the bug helped a scammer. A spokesperson told SecurityWeek that "we believe a scammer was using it to make their scam message seem more credible." The company described the bug as low-impact and said it may have been abused alongside specific spam messages.
Reporting on the advisory says two of the flaws came through WhatsApp's bug bounty program. WhatsApp also said it had no evidence of active exploitation at the time of disclosure. Those two points cut in different directions. The bounty reports show outside researchers are still finding bugs in the app, while the lack of exploitation evidence suggests the scam use was limited or hard to observe.
Which Android versions to install
The version thresholds below come from security-news summaries of the advisory. If you manage devices at scale, confirm them against WhatsApp's own notice before you roll out changes.
| Flaw | Vulnerable below | Platforms |
|---|---|---|
| CVE-2026-23871 | 2.26.17.4 | WhatsApp and WhatsApp Business for Android |
| CVE-2026-102769 | 2.26.35.74 | WhatsApp for Android |
| CVE-2026-44908 | WhatsApp for Android 2.26.23.74; WhatsApp Business for Android 2.26.23.70; WhatsApp for iOS 2.26.24.72; WhatsApp Business for iOS 2.26.23.72; WhatsApp for Mac 2.26.23.72 | Android, iOS and Mac |
The sources do not say whether iOS users were affected by CVE-2026-23871. The advisory's reported coverage points to Android and WhatsApp Business for Android, so iPhone users should check WhatsApp's own notice rather than assume they are clear.
How to update WhatsApp on Android and reduce scam risk
Follow these steps on each Android phone that runs WhatsApp or WhatsApp Business.
- Open the Google Play Store, search for WhatsApp or WhatsApp Business, and tap Update. Install updates only from the official store listing.
- Confirm the installed version. Open the app, go to Settings, then Help, then App info, and compare the number with the thresholds in the table.
- If you administer work devices, check that both apps are current on every managed phone. Reporting on the advisory notes that WhatsApp advised organizations to include messaging apps in their attack-surface inventories.
- Treat unexpected ad replies and links as suspect, even when they appear to come from a business you already know. Verify any request for money or login details through a separate channel, such as a phone number you already have saved.
The last step matters most for this flaw. Even a patched phone cannot stop a scammer from sending a convincing-looking message, so the habit of checking before acting remains the main defense.
What remains unknown about the scam campaign
The identity of the scammer, the size of the campaign and the number of people targeted are not public. The claim that scammers used the bug is a suspicion that WhatsApp has described, not a confirmed finding. Treat reports of real-world abuse as reported but unverified until WhatsApp or independent researchers publish more detail.
The version numbers are also worth watching. Different outlets have described the fixes in different ways, and only WhatsApp's own advisory can settle the details.
What comes next for WhatsApp patching and scam disruption
The bug surfaced during scam disruption work, which suggests platform security teams will keep finding weaknesses in the tools criminals use. Federal efforts are moving in the same direction. The DHS and DOJ Threat Disruption Center is focused on tracing scam crypto, a sign that the government is targeting the money side of these operations as well as the messaging side.
A fix only protects people who install it. Patching lags are a recurring problem, as the NGINX2Root flaws with public exploits show. For WhatsApp, the practical test is simple: how many Android phones show a fixed version within a week of this advisory.
Watch for two things next. The first is any update from WhatsApp that confirms or revises the scam-use claim. The second is whether the company says anything more about iOS coverage for CVE-2026-23871. Either would change how urgent this patch looks for different groups of users.




