News
WhatsApp patched three flaws, including an Android bug it suspects scammers used.
WhatsApp fixed three vulnerabilities, including an Android bug that can reveal a phone's IP address when a crafted ad-reply is shown. The company says it found that bug while disrupting a scam campaign.

Impact
- What was impacted
- Three WhatsApp flaws. CVE-2026-23871, in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4, can reveal a phone's IP address when a crafted Click to WhatsApp ad-reply is shown and the media comes from an address the attacker controls. CVE-2026-102769, an SQL injection in WhatsApp for Android before 2.26.35.74, can delete WhatsApp files stored on the phone if the recipient taps a crafted order-details message from an unofficial client, and can leak one bit about the chat database if the person is online when that message arrives. CVE-2026-44908, a certificate check for Meta AI confidential computing, affects WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before 2.26.23.72, WhatsApp for Android before 2.26.23.74, and WhatsApp Business for Android before 2.26.23.70.
- Who was impacted
- People and companies still on those app versions. WhatsApp suspects the IP-address bug was used with specific spam messages during a scam campaign. It says there is no evidence the SQL injection was exploited. The certificate bug would require an attacker already inside Meta infrastructure, and WhatsApp says the transparency ledger shows it was not used.
- What you need to do
- Update each app past the version this report names for it. For WhatsApp for Android, install 2.26.35.74 or newer, which is past every Android floor named for that app. For WhatsApp Business for Android, install 2.26.23.70 or newer. For WhatsApp for iOS, install 2.26.24.72 or newer. For WhatsApp Business for iOS and WhatsApp for Mac Desktop, install 2.26.23.72 or newer. Until WhatsApp for Android is updated, do not tap an unexpected order-details message. This report does not name another workaround.
WhatsApp patched three security flaws. The one it suspects was used in the wild is CVE-2026-23871, an incomplete check of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4. If a crafted Click to WhatsApp ad-reply is displayed in a chat and that message loads media from an address the attacker controls, the phone can reveal its IP address to the attacker. WhatsApp said the bug may have been abused together with specific spam messages. Its own security team found it while disrupting a scam campaign, and a spokesperson said they believe a scammer was using it so the scam message would look more credible. WhatsApp did not say how many people were targeted, or whether the scam succeeded.
The second flaw, CVE-2026-102769, is an SQL injection in WhatsApp for Android before 2.26.35.74. It runs when the recipient taps a specially crafted order-details message sent from an unofficial client, and WhatsApp says that can delete WhatsApp files stored on the phone. If the person is online when the malicious message arrives, the same bug can also leak one bit of information the attacker asked about the chat database, by timing a delivery receipt after a crash the message induces. This report describes that flaw only for WhatsApp for Android, not for Business, iOS, or Mac. WhatsApp says there is no evidence it has been exploited.
The third flaw, CVE-2026-44908, is in the certificate check WhatsApp uses for Meta AI's confidential computing, which the report ties to WhatsApp Private Processing. An attacker who was already positioned inside Meta infrastructure could have bypassed the hardware root of trust with a Versioned Chip Endorsement Key certificate that was not signed by the hardware maker's key. WhatsApp says any such certificate would first have had to be published to the third-party binary transparency ledger Private Processing uses, and that every certificate on that ledger still chains to the hardware root of trust. WhatsApp says that confirms the flaw was not exploited. It affects WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before 2.26.23.72, WhatsApp for Android before 2.26.23.74, and WhatsApp Business for Android before 2.26.23.70.
WhatsApp's advice is to keep the apps and the phones up to date. For WhatsApp for Android, install 2.26.35.74 or newer so all three Android floors in this report are cleared. For WhatsApp Business for Android, install 2.26.23.70 or newer. For WhatsApp for iOS, install 2.26.24.72 or newer. For WhatsApp Business for iOS and WhatsApp for Mac Desktop, install 2.26.23.72 or newer. Until the Android app is updated, do not tap an unexpected order-details message.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to three WhatsApp vulnerabilities disclosed together. Do not write or run an exploit or a proof of concept. Do not craft an ad-reply, an order-details message, a crash, or a certificate. Do not try to read a phone's IP address, time a delivery receipt, or query a chat database. Ask before pushing an app update to a fleet or signing people out. Facts from the report: - CVE-2026-23871 is incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4. A target's device can reveal its IP address if an attacker sends media from an attacker-controlled URL when a crafted Click to WhatsApp ad-reply is rendered and displayed in a message thread. WhatsApp said it may have been abused in conjunction with specific spam messages. Internal researchers on the WhatsApp Security Team found it while disrupting a scam campaign. A spokesperson said they believe a scammer was using it to make a scam message seem more credible. WhatsApp did not disclose the scale, or whether those efforts succeeded. Do not invent a victim count or a success rate. - CVE-2026-102769 is an SQL injection in WhatsApp for Android prior to 2.26.35.74. When a recipient taps a specially crafted order-details message sent from an unofficial client, locally stored WhatsApp files can be deleted. If the user is online when the malicious message is received, it can also leak one bit of information the attacker asked about the user's chat database, via an induced-crash delivery-receipt timing side channel. There is no evidence this vulnerability has been exploited. The report describes it only for WhatsApp for Android. Do not apply it to WhatsApp Business, iOS, or Mac. Do not describe the one bit as a copy of the chats. - CVE-2026-44908 is a trust-validation flaw in certificate verification for Meta AI's confidential computing infrastructure. It affects WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before 2.26.23.72, WhatsApp for Android before 2.26.23.74, and WhatsApp Business for Android before 2.26.23.70. A bad actor positioned within Meta infrastructure could have bypassed the hardware root of trust using a Versioned Chip Endorsement Key (VCEK) certificate not signed by the hardware manufacturer's key. Any such certificate would first have to be published to the third-party binary transparency ledger used by WhatsApp Private Processing. WhatsApp says the ledger shows every published VCEK certificate chains to the hardware root of trust, confirming no exploitation. Do not describe this as an attack any remote stranger can run. Do not tell me to audit Meta's ledger or rotate a Meta AI key. This report does not say to do that. - The only advice WhatsApp gave readers is to keep apps and devices up to date. Do not invent a workaround, a CVE score, or another fixed build. - Version floors, meaning a build at that number is no longer in the vulnerable "before" range: WhatsApp for Android 2.26.35.74 (this is also past 2.26.23.74 and 2.26.17.4). WhatsApp Business for Android 2.26.23.70 (this is also past 2.26.17.4; the SQL injection was not listed for Business). WhatsApp for iOS 2.26.24.72. WhatsApp Business for iOS and WhatsApp for Mac Desktop 2.26.23.72. Do not invent a later build number and call it required. Context: - What was impacted: WhatsApp app builds older than the versions above, in three different ways. - Who should care: anyone still running those builds. The IP-address bug is the one suspected in a scam. The other two have no evidence of exploitation, and the certificate bug needs a position inside Meta. - What to do: update each installed WhatsApp app to the floor named for it, and do not tap an unexpected order-details message on WhatsApp for Android until that app is updated. Do this in order. Ask before changing a managed fleet. Prefer read-only inventory first. Do not write or run an exploit or a proof of concept. 1. Inventory - List installed WhatsApp apps: WhatsApp for Android, WhatsApp Business for Android, WhatsApp for iOS, WhatsApp Business for iOS, and WhatsApp for Mac Desktop. Record the version. If a device is not in front of you, say so and stop. - Compare only against the floors above. Flag an app only when its version is below the floor named for that app. Do not flag WhatsApp Business, iOS, or Mac for CVE-2026-102769. 2. Contain - On a flagged WhatsApp for Android install, tell the user not to tap an unexpected order-details message until the app is updated. Do not send a test message. - Do not propose disabling Meta AI, blocking ads, or changing a certificate store. This report does not support those steps. 3. Remediate - Plan an update to the floor named for each flagged app, or any newer build the store offers. Ask before pushing that update or signing anyone out. Do not invent a package name or a build the report did not name. 4. Verify - After an update I asked you to perform, read the version again and compare it to the same floor. - If I did not ask you to change anything, report the current versions only. 5. Report back - Which apps are installed, their versions, which are below the named floor, what you changed, and that the IP-address bug is the only one WhatsApp suspects was used. Do not invent CVEs, victim counts, or signs of a past intrusion. If a check needs access I have not given you, say what you need and stop.