WhatsApp fixes three flaws with different risks: what the advisories actually say
Three vulnerabilities involve three different scenarios: WhatsApp’s November security advisories distinguish IP-address exposure, an Android database flaw and verification of the infrastructure used by Meta AI.
SecurityWeek’s report, published on 20 November and updated on 21 November, also includes a spokesperson’s explanation that one flaw was discovered while disrupting a scam campaign.
## The advertising-related flaw
CVE-2026-23871 affects WhatsApp and WhatsApp Business for Android before version 2.26.17.4: incomplete URL validation in Click to WhatsApp ad replies could expose the IP address when media from an attacker-controlled address was displayed.
The advisory says the issue may have been abused alongside specific spam messages.
The spokesperson told SecurityWeek that the team believed a scammer was using it to make a message appear more credible: that is the company’s account, not independent verification of every attack.
## The order message required interaction
CVE-2026-102769 affects WhatsApp for Android before 2.26.35.74 and could be triggered by tapping a specially crafted “order details” message from an unofficial client.
The advisory describes possible deletion of local files and, only if the user was online when the message arrived, leakage of one bit of information about the database through a timing side channel.
WhatsApp says it has seen no evidence of exploitation in the wild for this flaw.
This does not establish that all chats were read.
## Meta AI: a trust boundary, not a confirmed intrusion
CVE-2026-44908 concerns certificate-chain validation in remote attestation for Meta AI’s confidential computing backend.
The attacker described would need to be positioned within Meta infrastructure, and the certificate would first have to appear in a third-party transparency ledger.
According to WhatsApp, all published certificates chain to the hardware root of trust, confirming no exploitation of that path.
The practical step is to update the client through its official channel, checking the platform and version: the advisories list different thresholds for Android, iOS, Mac and Business clients.
A documented vulnerability, possible abuse and a confirmed compromise are not the same story.
