# WhatsApp for Android flaw CVE-2026-23871 (Click to WhatsApp ads IP disclosure) uncovered while disrupting scam campaign; CVE-2026-102769 and CVE-2026-44908 also fixed

> WhatsApp fixed CVE-2026-23871, a low-impact incomplete-URL-validation flaw in the Click to WhatsApp ad-reply feature of WhatsApp and WhatsApp Business for Android (before 2.26.17.4) that WhatsApp believes a scammer abused to make scam messages look more credible. The November 2026 advisory update also fixes two medium-impact issues (CVE-2026-102769 SQL injection and CVE-2026-44908 remote-attestation certificate validation) with no evidence of exploitation.

- **Published:** 2026-11-20T16:17:20Z
- **Last reviewed:** 2026-11-21T07:07:44.009Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6598
- **ID:** TL-2026-6598
- **Severity:** MEDIUM (CVSS 6.8)
- **Category:** VULNERABILITY
- **Status:** PATCHED
- **Detections:** 9 (1 shown free below) · **IOCs:** 13
- **CVEs:** CVE-2026-23871, CVE-2026-102769, CVE-2026-44908

## Description

WhatsApp's November 2026 security advisory update lists three CVEs. The headline flaw, CVE-2026-23871, affects WhatsApp for Android and WhatsApp Business for Android before version 2.26.17.4. Incomplete validation of external ad-reply URLs could cause a target's device to reveal its IP information to an attacker. Exploitation required the attacker to send media from an attacker-controlled URL and a crafted Click to WhatsApp ad-reply message to be rendered and displayed in a message thread. The advisory states the issue 'may have been abused in conjunction with specific spam messages'. It was found by internal researchers on the WhatsApp Security Team. A WhatsApp spokesperson told SecurityWeek the team found the issue while disrupting a scam campaign and believes a scammer used it to make their scam message seem more credible. No scammer, campaign, or infrastructure is named, and no CVSS score is published; SecurityWeek characterizes the issue as low-impact.

CVE-2026-102769 (ID verified against the WhatsApp advisory page) is a SQL injection in WhatsApp for Android prior to 2.26.35.74. Tapping a specially crafted 'order details' message sent from an unofficial client could delete locally stored WhatsApp files. If the recipient was online when the message arrived, it could also leak one bit of information, chosen by the attacker, about the user's chat database through a crash-based delivery-receipt timing side channel. It was reported by an external researcher through the Meta bug bounty program, and WhatsApp states it has not seen evidence of exploitation in the wild.

CVE-2026-44908 is an improper certificate chain-of-trust check in the remote-attestation verifier that WhatsApp clients use to establish trust with Meta AI's confidential computing backend (WhatsApp Private Processing). It could have allowed someone positioned within Meta infrastructure to bypass the hardware root of trust by presenting clients with a VCEK certificate signed by a key other than the hardware manufacturer's. Such a certificate would first have had to be published to a third-party binary transparency ledger; WhatsApp says the ledger shows every published VCEK certificate chains to the hardware root of trust, confirming no exploitation. Fixed versions per the advisory: WhatsApp for iOS 2.26.24.72; WhatsApp Business for iOS and WhatsApp for Mac 2.26.23.72; WhatsApp for Android 2.26.23.74; WhatsApp Business for Android 2.26.23.70. It was found by internal Meta researchers.

Defensive takeaway: ensure Android WhatsApp and WhatsApp Business clients are updated to current releases, and treat unsolicited Click to WhatsApp ad-reply messages and 'order details' messages from unknown senders with suspicion. There are no network or file IOCs published for this threat.

## MITRE ATT&CK

- T1590.005 IP Addresses
- T1566.003 Spearphishing via Service
- T1204 User Execution
- T1684.001 Impersonation
- T1553 Subvert Trust Controls
- T1005 Data from Local System
- T1485 Data Destruction
- T1583 Acquire Infrastructure
- T1664 Exploitation for Initial Access
- T1658 Exploitation for Client Execution
- T1409 Stored Application Data

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**WhatsApp Android Builds Vulnerable to CVE-2026-23871 / CVE-2026-102769 / CVE-2026-44908 — Exploitation Exposure** (`TL-2026-6598-SPL-001`)

Flags Android devices running com.whatsapp or com.whatsapp.w4b below the fixed releases for the three November 2026 WhatsApp CVEs. CVE-2026-23871 (Click to WhatsApp ad-reply incomplete URL validation) was probably abused by a scammer in spam messages; CVE-2026-102769 (order-details SQL injection) needs a tapped message from an unofficial client. Identifies the population exposed to the exploitation chain (TL-2026-6598).

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1566.003, T1204, T1590.005
- **Data sources:** intune mobile app inventory (index=mdm, sourcetype=ms:intune:mobileapp_inventory), Defender TVM DeviceTvmSoftwareInventory
- **Severity:** medium
- **Confidence:** medium

### Splunk SPL

````spl
index=mdm sourcetype="ms:intune:mobileapp_inventory" os_platform="Android" (app_package="com.whatsapp" OR app_package="com.whatsapp.w4b") earliest=-24h
```Build a sortable number from a dotted version: a.b.c.d becomes a*1e9+b*1e6+c*1e3+d```
| eval p=split(app_version,"."), vnum=tonumber(mvindex(p,0))*1000000000+tonumber(mvindex(p,1))*1000000+tonumber(mvindex(p,2))*1000+tonumber(mvindex(p,3))
| eval cves=mvappend(if(vnum<2026017004,"CVE-2026-23871",null()), if(app_package="com.whatsapp" AND vnum<2026035074,"CVE-2026-102769",null()), if((app_package="com.whatsapp" AND vnum<2026023074) OR (app_package="com.whatsapp.w4b" AND vnum<2026023070),"CVE-2026-44908",null()))
| where isnotnull(cves)
| stats latest(app_version) as installed_version values(cves) as cves latest(_time) as last_seen by device_id user app_package
| convert ctime(last_seen)
| sort - last_seen
````

### Microsoft KQL

```kql
// Snapshot table: no TimeGenerated filter; Defender TVM reports current state.
DeviceTvmSoftwareInventory
| where OSPlatform has "Android"
| where SoftwareName has_any ("whatsapp", "w4b")
| extend IsBusiness = SoftwareName has_any ("w4b", "business"), v = parse_version(SoftwareVersion)
| extend CVE_2026_23871 = v < parse_version("2.26.17.4"),
         CVE_2026_102769 = (not(IsBusiness) and v < parse_version("2.26.35.74")),
         CVE_2026_44908 = iff(IsBusiness, v < parse_version("2.26.23.70"), v < parse_version("2.26.23.74"))
| where CVE_2026_23871 or CVE_2026_102769 or CVE_2026_44908
| project DeviceId, DeviceName, OSPlatform, SoftwareName, SoftwareVersion, CVE_2026_23871, CVE_2026_102769, CVE_2026_44908
```

### Sigma

```yaml
title: WhatsApp for Android Build Vulnerable To CVE-2026-23871 / CVE-2026-102769 / CVE-2026-44908
id: 6f1c2a54-3b7e-4d0a-9c11-5a2e8f7b0c01
status: experimental
description: Detects Android WhatsApp or WhatsApp Business builds below the fixed releases for CVE-2026-23871 (Click to WhatsApp ad-reply URL validation, fixed 2.26.17.4), CVE-2026-102769 (order-details SQL injection, fixed 2.26.35.74) and CVE-2026-44908 (attestation certificate chain check, fixed 2.26.23.74 and Business 2.26.23.70).
references:
    - https://www.whatsapp.com/security/advisories/2026/
    - https://www.securityweek.com/whatsapp-fixes-flaw-uncovered-while-disrupting-scam-campaign/
author: Threadlinqs Team
date: 2026-11-20
tags:
    - attack.initial-access
    - attack.t1566.003
    - attack.execution
    - attack.t1204
    - cve.2026.23871
    - cve.2026.102769
    - cve.2026.44908
logsource:
    product: intune
    service: mobileapp_inventory
detection:
    selection_wa:
        app_package: 'com.whatsapp'
        app_version|re: '^(1\.|2\.(\d|1\d|2[0-5])\.|2\.26\.(\d|[12]\d|3[0-4])\.|2\.26\.35\.(\d|[1-6]\d|7[0-3])$)'
    selection_w4b:
        app_package: 'com.whatsapp.w4b'
        app_version|re: '^(1\.|2\.(\d|1\d|2[0-5])\.|2\.26\.(\d|1\d|2[0-2])\.|2\.26\.23\.(\d|[1-6]\d)$)'
    condition: selection_wa or selection_w4b
falsepositives:
    - Devices pending the next MDM app update cycle
    - Test or lab devices intentionally pinned to older builds
level: medium

```

**Known false positives:**

- Devices awaiting the next managed app update cycle
- Lab or test devices pinned to old builds

**Tuning notes:** Field names (app_package, app_version, device_id) assume an Intune app-inventory export; remap to your MDM. Version math assumes four numeric parts below 1000. Exclude devices with an approved exception. Fixed-version thresholds come from the vendor advisory in research.json.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- WhatsApp CVE-2026-23871 / 102769 / 44908 Vulnerability Findings — Exploitation Exposure (locked: unlock with TL Creds)
- WhatsApp Local Chat Database Deletion — CVE-2026-102769 Impact Artifact (locked: unlock with TL Creds)
- WhatsApp Client Contacting First-Seen or IP-Literal Host — CVE-2026-23871 Scam Infrastructure (locked: unlock with TL Creds)
- WhatsApp Android Below 2.26.35.74 — CVE-2026-102769 Exposure (locked: unlock with TL Creds)
- WhatsApp Order-Details Message Error — CVE-2026-102769 Trigger Indicator (locked: unlock with TL Creds)
- WhatsApp Private Processing Attestation Failure — CVE-2026-44908 Trust Subversion (locked: unlock with TL Creds)
- WhatsApp Android Crash with SQLite Error — CVE-2026-102769 Post-Exploitation Indicator (locked: unlock with TL Creds)
- WhatsApp Client Fetching Media From Rare Non-Meta Host — CVE-2026-23871 IP Disclosure (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [WhatsApp Fixes Flaw Uncovered While Disrupting Scam Campaign (SecurityWeek)](https://www.securityweek.com/whatsapp-fixes-flaw-uncovered-while-disrupting-scam-campaign/)
- [WhatsApp Security Advisories 2026](https://www.whatsapp.com/security/advisories/2026/)
- [What we learned about TEE security from auditing WhatsApp's Private Inference (Trail of Bits)](https://blog.trailofbits.com/2026/04/07/what-we-learned-about-tee-security-from-auditing-whatsapps-private-inference/)
- [Building Private Processing for AI tools on WhatsApp (Meta Engineering)](https://engineering.fb.com/2025/04/29/security/building-private-processing-for-ai-tools-on-whatsapp/)
- [Meta Private Processing technical whitepaper](https://ai.meta.com/static-resource/private-processing-technical-whitepaper)
- [WhatsApp Private Inference pre-launch audit uncovered critical flaws (CyberInsider)](https://cyberinsider.com/whatsapp-private-inference-pre-launch-audit-uncovered-critical-flaws/)
- [Update WhatsApp now: two new flaws could expose you to malicious files (Malwarebytes, May 2026 advisory update)](https://www.malwarebytes.com/ja/blog/news/2026/05/update-whatsapp-now-two-new-flaws-could-expose-you-to-malicious-files)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple and Gold in full, 2 calls a day on a free account): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6598
