WhatsApp patched three security vulnerabilities this month, the most defining of which its own security team came across while actively disrupting an ongoing fraud campaign. The vulnerability had been helping scammers make their messages look more convincing to targets, and the company fixed it after finding it in the field.
Incomplete validation of external ad-reply URLs in Click to WhatsApp messages. A crafted message could cause the target's device to reveal its IP address to an attacker-controlled server.
The flaw lives in WhatsApp's handling of Click to WhatsApp ads, a Meta advertising product that routes people from paid placements directly into WhatsApp conversations with businesses. The underlying problem was that the app failed to fully validate external URLs embedded in ad-reply messages. If an attacker sent media hosted on a server they controlled alongside a crafted ad-reply message, the target's device would fetch that media when the message rendered in the thread, exposing the recipient's IP address in the process.
"Our team found this issue while disrupting a scam campaign." ~ WhatsApp spokesperson
The company's advisory noted the vulnerability "may have been abused in conjunction with specific spam messages," though WhatsApp did not describe the nature of the campaign in detail. IP address exposure can appear minor, but in targeted fraud operations it has real utility. It can confirm a target is in the expected country, verify that a victim account is currently active, and feed into the profiling that makes follow-up social engineering more persuasive.
A Crafted Message That Could Delete Local Files
SQL injection triggered by an "order details" message sent from an unofficial client. Could delete locally stored WhatsApp files, with an additional timing side channel if the recipient was online.
The second flaw was reported by an external researcher through Meta's bug bounty program. It involved a SQL injection vulnerability in the app's handling of "order details" messages, a feature that lets sellers share product information inside a WhatsApp chat. If the message was crafted by an unofficial client and tapped by the recipient, the app could be manipulated into deleting locally stored WhatsApp files.
Beyond file deletion, there was an additional wrinkle: if the target happened to be online at the exact moment of receipt, the attacker could infer one bit of information about the contents of the chat database through a timing side channel based on delivery receipts. WhatsApp rates the flaw as medium severity and says it has found no evidence of exploitation in the wild before the fix was issued.
The requirement that the malicious message originate from an unofficial WhatsApp client limits the attack surface. Standard WhatsApp apps would not generate such a message in normal use, meaning an attacker would need to operate through a modified third-party application to trigger the vulnerability on someone else's device.
A Flaw in WhatsApp's AI Privacy Architecture
Improper certificate chain-of-trust validation in the remote-attestation verifier for Meta AI's confidential computing backend. A certificate not signed by the hardware manufacturer's key could theoretically bypass the hardware root of trust.
The third flaw sits inside a newer part of WhatsApp's infrastructure: Private Processing, the confidential computing system the company introduced for running Meta AI tools on message data without exposing that data to Meta itself. The premise is that AI features like message summarization run inside a Trusted Execution Environment where even Meta engineers cannot read the content being processed.
The system's integrity rests on remote attestation. Before a device sends any data to the secure environment, it checks the attestation measurements of the code running inside against a third-party binary transparency ledger, confirming the environment is running approved software before any messages are handed over. The flaw in CVE-2026-44908 meant that someone inside Meta's own infrastructure could theoretically bypass the hardware root of trust by presenting a certificate not signed by the hardware manufacturer's key.
WhatsApp says the attack would not have been invisible. Any such certificate would first need to be published to that same third-party transparency ledger before a client would accept it, and the ledger is designed to be auditable by outside parties. The company reviewed the published certificates and confirmed all of them trace back to the legitimate hardware root of trust. "Confirming no exploitation," the advisory states. Meta's internal security researchers found this one themselves.
Users running WhatsApp for Android should update to version 2.26.35.74 or later to cover all three November vulnerabilities. iOS and Mac users are covered against the Private Processing flaw by their respective patched versions. Updates are available through the standard app stores.