Key facts
- Meta owns WhatsApp, which patched CVE-2026-23871, a flaw in how WhatsApp and WhatsApp Business for Android before version 2.26.17.4 checked external ad-reply URLs.
- WhatsApp's security team discovered the flaw while disrupting a scam campaign.
- WhatsApp said the flaw could expose a target's IP information to an attacker when a crafted ad-reply message appeared in a message thread.
- Click to WhatsApp ads link the flaw to both WhatsApp and WhatsApp Business on Android.
WhatsApp, which Meta owns, patched CVE-2026-23871, a common vulnerabilities and exposures identifier, in WhatsApp and WhatsApp Business, Meta’s app for companies, for Android before version 2.26.17.4 in its November security advisory after its security team found the flaw while disrupting a scam campaign. The flaw concerned how the apps checked external ad-reply URLs, web addresses tied to ad replies, and versions before 2.26.17.4 of WhatsApp and WhatsApp Business for Android were affected. WhatsApp’s November security advisory fixed three flaws in total. WhatsApp also credited its internal Security Team researchers with discovering and reporting the flaw.
The flaw could expose a target’s IP information to an attacker when a crafted ad-reply message appeared in a message thread, WhatsApp said. An attacker could host media on their own server and deliver it through a crafted ad-reply message. Click to WhatsApp ads link the flaw to both WhatsApp and WhatsApp Business on Android.
A scammer was using the flaw to make scam messages seem more credible, WhatsApp believes. 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 it succeeded. According to WhatsApp, users should update their apps and devices.
On Nov. 20, 2026, WhatsApp rated CVE-2026-23871 as low-impact and rated CVE-2026-102769 and CVE-2026-44908 as medium-impact. WhatsApp said it works continuously to strengthen its systems and acknowledges contributions from researchers paid through its bug bounty program.
WhatsApp also patched CVE-2026-102769, an SQL injection, a flaw that lets an attacker interfere with database queries, in WhatsApp for Android before 2.26.35.74 triggered by a crafted “order details” message from an unofficial client, a version of the app not released by WhatsApp. The flaw could delete locally stored WhatsApp files and, if the user was online, leak one bit of chat-database information, data from the app’s local message database, through a timing side channel, a method that infers data from how long an operation takes. WhatsApp has seen no evidence that CVE-2026-102769 was exploited in the wild. An external researcher reported CVE-2026-102769 through Meta’s bug bounty program.
The company also patched CVE-2026-44908, a trust-validation flaw in certificate verification for Meta AI’s confidential computing infrastructure. The flaw affects WhatsApp for iOS before 2.26.24.72 and WhatsApp Business for iOS and WhatsApp for Mac Desktop before v2.26.23.72. WhatsApp said it also affects WhatsApp for Android before v2.26.23.74 and WhatsApp Business for Android before v2.26.23.70.
WhatsApp also said someone inside Meta infrastructure could bypass the hardware root of trust, the foundational security layer in a device’s processor, with a VCEK certificate, a virtual key used in trusted computing, unsigned by the hardware maker’s key. WhatsApp said the hardware root of trust is where every VCEK certificate connects via the third-party transparency ledger, a public log that records certificates, confirming no exploitation.
Security Affairs said just one of the three flaws saw real-world scam use and described it as the least technically serious of the three. Security Affairs also said scammers do not always need serious vulnerabilities or device access because a convincing message can deceive a victim. In May, WhatsApp fixed an Instagram Reels message bug and the Windows attachment-spoofing trick reported through Meta’s bug bounty program, with no evidence of exploitation.

Join the discussion