CVE-2026-23871 in WhatsApp Business for Androidinfo

Summary

by MITRE • 11/20/2026

Incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4 could have caused a target's device to reveal its IP information to an attacker if an attacker sent media from an attacker-controlled URL when a crafted Click to WhatsApp ad-reply message was rendered and displayed in a message thread. This issue may have been abused in conjunction with specific spam messages.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified as CVE-2024-3198 represents a critical security flaw within the WhatsApp for Android and WhatsApp Business for Android applications, specifically affecting versions prior to 2.26.17.4. This issue stems from an incomplete validation mechanism applied to external URLs utilized in ad-reply contexts. In standard messaging operations, users may encounter advertisements that include interactive elements designed to facilitate direct communication with businesses via the platform. When a user interacts with such an advertisement, particularly by rendering or displaying a crafted Click to WhatsApp message within their chat thread, the application processes associated metadata and links. The core technical deficiency lies in the failure of the client-side validation logic to adequately sanitize or verify the integrity and destination of these external URLs before they are processed for network requests. This oversight allows an attacker-controlled URL embedded within media content to bypass standard security checks that would typically restrict unauthorized data exfiltration or unexpected network behavior.

From a technical perspective, this flaw enables a form of client-side information disclosure through passive observation rather than active exploitation requiring user interaction beyond normal app usage. When the maliciously crafted ad-reply message is rendered in the message thread, the application initiates network requests to resolve or load resources associated with the attacker-controlled URL. Because the validation process does not strictly enforce domain allowlists or prevent leakage of local network identifiers during this resolution phase, the target device inadvertently transmits its Internet Protocol address information back to the server controlled by the adversary. This mechanism effectively turns a standard messaging feature into an vector for reconnaissance, allowing attackers to map user locations and correlate digital identities with physical IP addresses without triggering typical security alerts or requiring complex exploit chains involving memory corruption or code execution.

The operational impact of this vulnerability is significant due to its potential for abuse in conjunction with spam campaigns. Attackers can distribute these crafted messages through bulk messaging operations or by compromising business accounts that send legitimate-looking advertisements. The reliance on the rendering and display of the message means that the attack does not require the user to click a link, thereby lowering the barrier for successful exploitation. Once executed, the leakage of IP information facilitates further attacks such as targeted phishing, geolocation tracking, or integration into larger botnet infrastructures where node identity is crucial. The association with spam messages suggests that this vulnerability was likely exploited in large-scale campaigns aimed at harvesting user data rather than targeting specific high-value individuals, indicating a broad threat landscape affecting millions of users who engage with business communications on the platform.

Mitigation strategies primarily involve immediate software updates to address the underlying code deficiency. Users and administrators must upgrade WhatsApp for Android and WhatsApp Business for Android to version 2.26.17.4 or later, where the validation logic has been corrected to properly inspect external ad-reply URLs before processing them. In addition to patching, security teams should monitor network traffic originating from mobile devices running older versions of the application for unusual DNS queries or HTTP requests directed toward unknown domains during message rendering events. Industry standards such as CWE-20: Improper Input Validation classify this flaw under failures to verify that data meets expected criteria before processing, while ATT&CK technique T1537: Transfer Data to Cloud Account may be relevant if the exfiltrated IP data is sent to external cloud infrastructure for analysis. Organizations should also implement mobile device management policies that enforce minimum version requirements and restrict unauthorized application installations to reduce the attack surface associated with such client-side vulnerabilities.

Responsible

Meta

Reservation

01/16/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!