On this page (7 sections)
WhatsApp has fixed CVE-2026-23871, a low-severity flaw in its Android apps. According to WhatsApp's advisory text as reproduced in the GitHub Advisory Database, a crafted Click to WhatsApp ad-reply message could cause a device to reveal its IP information to an attacker. WhatsApp says its own security team found the problem while disrupting a scam campaign.
The practical risk to most people is small, but the bug matters to anyone who runs Click to WhatsApp ads, handles customer chats on WhatsApp Business, or manages company phones. The fix is simply to update the app.
What happened
The advisory describes incomplete validation of external ad-reply URLs. If an attacker sent media from an attacker-controlled URL inside a crafted Click to WhatsApp ad-reply message, and that message was rendered and displayed in a message thread, the target's device could reveal its IP information to the attacker. The advisory adds that the issue may have been abused in conjunction with specific spam messages.
According to The Hacker News, internal researchers on the WhatsApp Security Team discovered and reported it. A WhatsApp spokesperson told the outlet the flaw was found while disrupting a scam campaign and that the company believes a scammer was using it to make the scam message seem more credible. WhatsApp did not say how widespread the activity was or whether it worked. SecurityWeek carries the same spokesperson statement, so treat the two reports as one vendor claim rather than independent confirmation.
Technical details in plain terms
The weakness is a validation gap. When a chat shows content that comes from an external address, the app has to decide whether that address is safe to fetch. Here, the check on the ad-reply URL was incomplete, so the app could be steered into loading media from a server the attacker controls. Any device that fetches content from a server tells that server its IP address, which is why the outcome is an IP disclosure and not code execution.
The CVSS vector in the GitHub advisory reflects that limited impact: network attack vector, low complexity, low privileges required, user interaction required, and a low confidentiality impact with no integrity or availability impact. No CWE is listed, and the advisory shows no affected-package data beyond the Android version boundary.
Other WhatsApp fixes announced alongside it
Reporting on the same advisory batch mentions two other issues, neither of which WhatsApp says was exploited. The Hacker News describes CVE-2026-102769 as an SQL injection in WhatsApp for Android before 2.26.35.74, triggered by tapping a crafted "order details" message from an unofficial client, which could delete locally stored WhatsApp files. It describes CVE-2026-44908 as a trust-validation flaw in certificate verification for Meta AI's confidential computing infrastructure, affecting several WhatsApp builds on iOS, Mac and Android. Check WhatsApp's own 2026 advisories page for the exact version lists.
Who is realistically exposed
- Android users of WhatsApp or WhatsApp Business running a version older than 2.26.17.4.
- Businesses that advertise with Click to WhatsApp ads and receive ad-reply messages, since the bug involves that message type.
- Staff and owners who use WhatsApp on phones that also hold work email, admin panels or hosting logins. The bug itself discloses only IP information, but scammers use credibility tricks to push people toward phishing links.
Nothing in the research indicates that iOS or desktop apps are affected by this specific CVE.
What to do now
- Open Google Play, search for WhatsApp (and WhatsApp Business if you use it), and install any pending update.
- In the app, open Settings, then Help, then App info, and confirm the version is 2.26.17.4 or newer.
- If you manage company-owned Android phones, check your mobile device management console for the installed WhatsApp version and push the update.
- Turn on automatic app updates in Google Play for WhatsApp and WhatsApp Business.
- Remind staff that an ad-reply message that looks official or credible is not proof it is genuine. Do not tap unexpected links or share codes.
- If you run Click to WhatsApp ads, review the incoming ad-reply messages for unfamiliar senders or odd media and report suspicious ones to WhatsApp.
Detection and monitoring
There is no server-side artifact to hunt for on your website, because this is a client-side app bug. What you can watch is the scam activity around it. Scammers who want to look credible often impersonate your brand, so keep an eye on lookalike domains, unexpected changes to your DNS and certificates, and customer reports of odd WhatsApp messages that claim to come from you.
If you want help with the website side, a free SSL certificate checker lets you confirm your public certificate looks right, and Webforta Monitor can alert on certificate and DNS changes. Neither addresses this WhatsApp flaw itself. For broader guidance on spotting fraud aimed at your customers, see small business website security.
Bottom line
CVE-2026-23871 is a low-severity bug with a small direct impact, but it is a useful example of how scammers look for small flaws that make a fraudulent message feel real. Updating to 2.26.17.4 or later closes this one. WhatsApp's advice, as reported, is to keep apps and devices up to date.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
