CVE-2026-102769 in WhatsApp Business for Androidinfo

Summary

by MITRE • 11/20/2026

A SQL injection vulnerability when the recipient tapped on a specially crafted “order details” message from an unofficial client in WhatsApp for Android prior to version 2.26.35.74 could have allowed deletion of locally-stored WhatsApp files and, only if the user is online at time of receipt, leaked one bit of information asked by the attacker about the user’s chat database via an induced-crash delivery receipt timing sidechannel. We have not seen evidence of exploitation in the wild.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability described involves a critical SQL injection flaw within WhatsApp for Android prior to version 2.26.35.74, specifically triggered when a user interacts with a maliciously crafted message labeled as order details from an unofficial client. This security defect allows an attacker who sends such a specially constructed payload to execute arbitrary SQL commands on the local database of the victim's device. The primary consequence of this injection is the ability to delete locally stored WhatsApp files, which can result in significant data loss for the user by removing chat histories and associated media that are not backed up or synchronized with cloud services. This represents a severe integrity violation where an external actor gains unauthorized control over local application state through input validation failures in how message content is parsed and processed before database interaction.

Beyond direct file deletion, the vulnerability facilitates a sophisticated timing side-channel attack aimed at exfiltrating sensitive information from the user's chat database. The attacker can leak one bit of information per interaction by inducing specific crash behaviors dependent on whether the recipient is online when receiving the malicious message. This mechanism relies on analyzing delivery receipts and their timing to infer data about the contents of the chat database, demonstrating a complex exploitation technique that combines application logic flaws with network-level observations. Such side-channel attacks are particularly dangerous because they can bypass traditional access controls by leveraging subtle differences in system behavior rather than direct memory or file read operations.

From an industry standard perspective, this vulnerability aligns closely with CWE-89 Improper Neutralization of Special Elements used in an SQL Command, which highlights the failure to properly sanitize user-supplied input before incorporating it into database queries. The exploitation method involving timing analysis for data exfiltration corresponds to ATT&CK technique T1530 Data from Local System Extraction, specifically through indirect methods that do not involve direct file access but rather inference based on system responses. Additionally, the ability to delete local files relates to CWE-732 Incorrect Permission Assignment for Critical Resource, as it allows unauthorized modification of application data stores.

The operational impact is substantial despite the lack of evidence indicating widespread exploitation in the wild at the time of disclosure. Users are exposed to potential permanent loss of personal communication history and privacy breaches through the side-channel leakage mechanism. The requirement that the user must be online for the information leak adds a layer of complexity but does not mitigate the risk, as active users remain vulnerable to both data destruction and subtle intelligence gathering by attackers targeting high-value individuals or organizations using unofficial clients who may have weaker security postures.

Mitigation strategies primarily involve upgrading WhatsApp to version 2.26.35.74 or later, which addresses the underlying SQL injection flaw through improved input validation and parameterized query usage. Users should avoid interacting with messages from unofficial or untrusted sources that exhibit unusual formatting or content structures designed to trigger application anomalies. Furthermore, maintaining regular backups of chat data can mitigate the impact of file deletion attacks by allowing restoration of lost information. Security teams monitoring for this vulnerability should look for indicators of compromise related to unexpected database operations and anomalous timing patterns in message delivery receipts within their network traffic logs.

Responsible

Meta

Reservation

09/29/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!