Threat reportVulnerabilityTL-2026-6598
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.
Key facts
| Identifiers | TL-2026-6598, CVE-2026-23871, CVE-2026-102769, CVE-2026-44908 |
|---|---|
| Severity | MEDIUM |
| CVSS | 6.8 |
| First disclosed | |
| Affected products | Meta WhatsApp for Android; Meta WhatsApp Business for Android; Meta WhatsApp for iOS; Meta WhatsApp Business for iOS and WhatsApp for Mac Desktop |
| Weaknesses (CWE) | CWE-20, CWE-89, CWE-295, CWE-918, CWE-296 |
| Tools | Unofficial WhatsApp client |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1204 User Execution, T1409 Stored Application Data, T1485 Data Destruction, T1553 Subvert Trust Controls, T1566.003 Spearphishing via Service, T1583 Acquire Infrastructure, T1590.005 IP Addresses, T1658 Exploitation for Client Execution, T1664 Exploitation for Initial Access, T1684.001 Impersonation |
| Motivation | FINANCIAL |
| Target sectors | consumer, small business, telecoms |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 7 cited sources |
Detection coverage
As of 2026-11-21, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6598 across Splunk SPL, Microsoft KQL and Sigma, covering 13 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: WhatsApp Android Builds Vulnerable to CVE-2026-23871 / CVE-2026-102769 / CVE-2026-44908 — Exploitation Exposure
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
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_seenMicrosoft 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_44908Sigma
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.
- WhatsApp CVE-2026-23871 / 102769 / 44908 Vulnerability Findings — Exploitation Exposure · unlock with TL Creds
- WhatsApp Local Chat Database Deletion — CVE-2026-102769 Impact Artifact · unlock with TL Creds
- WhatsApp Client Contacting First-Seen or IP-Literal Host — CVE-2026-23871 Scam Infrastructure · unlock with TL Creds
- WhatsApp Android Below 2.26.35.74 — CVE-2026-102769 Exposure · unlock with TL Creds
- WhatsApp Order-Details Message Error — CVE-2026-102769 Trigger Indicator · unlock with TL Creds
- WhatsApp Private Processing Attestation Failure — CVE-2026-44908 Trust Subversion · unlock with TL Creds
- WhatsApp Android Crash with SQLite Error — CVE-2026-102769 Post-Exploitation Indicator · unlock with TL Creds
- WhatsApp Client Fetching Media From Rare Non-Meta Host — CVE-2026-23871 IP Disclosure · unlock with TL Creds
Indicators of compromise
As of 2026-11-21, Threadlinqs Intelligence tracks 13 indicators of compromise for TL-2026-6598.
Technical analysis
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 techniques by tactic:
Collection
T1005 Data from Local System; T1409 Stored Application Data
Execution
T1204 User Execution; T1658 Exploitation for Client Execution
Impact
defense-impairment
Initial Access
T1566.003 Spearphishing via Service; T1664 Exploitation for Initial Access
Resource Development
Reconnaissance
Defense Evasion
Remediation
Patches
- CVE-2026-23871: WhatsApp / WhatsApp Business for Android 2.26.17.4 or later
- CVE-2026-102769: WhatsApp for Android 2.26.35.74 or later
- CVE-2026-44908: WhatsApp for iOS 2.26.24.72; Business for iOS and Mac 2.26.23.72; Android 2.26.23.74; Business for Android 2.26.23.70 (or later)
Immediate actions
- Update WhatsApp and WhatsApp Business for Android to a current release (at least 2.26.35.74 covers both the CVE-2026-23871 and CVE-2026-102769 thresholds)
- Update WhatsApp for iOS, WhatsApp Business for iOS and WhatsApp for Mac to versions at or above those listed for CVE-2026-44908
Workarounds
- No vendor workaround published; block and report suspicious senders and avoid tapping unexpected order-details messages
Longer-term hardening
- Enforce mobile application patch compliance through MDM for managed devices running WhatsApp
- Train users to distrust unsolicited ad-reply or order-details messages from unknown senders and to report them via WhatsApp
Affected and fixed versions
- Meta — WhatsApp for Android
Vulnerable versions: before 2.26.17.4 (CVE-2026-23871); prior to 2.26.35.74 (CVE-2026-102769); before 2.26.23.74 (CVE-2026-44908)
Fixed in: 2.26.17.4; 2.26.35.74; 2.26.23.74 - Meta — WhatsApp Business for Android
Vulnerable versions: before 2.26.17.4 (CVE-2026-23871); before 2.26.23.70 (CVE-2026-44908)
Fixed in: 2.26.17.4; 2.26.23.70 - Meta — WhatsApp for iOS
Vulnerable versions: before 2.26.24.72 (CVE-2026-44908)
Fixed in: 2.26.24.72 - Meta — WhatsApp Business for iOS and WhatsApp for Mac Desktop
Vulnerable versions: before 2.26.23.72 (CVE-2026-44908)
Fixed in: 2.26.23.72
Timeline
Last updated · 2 updates · revalidated 2× · latest source
- Meta publishes its engineering description of WhatsApp Private Processing, the confidential-computing backend whose remote-attestation verifier is later affected by CVE-2026-44908.
- NCC Group report on the Meta WhatsApp message summarization / Private Processing security review is dated 2025-08-27.
- Trail of Bits publishes lessons from auditing WhatsApp's Private Inference, including attestation freshness findings addressed before launch.
- NVD SSVC records from a CISA coordinator list exploitation 'none' for all three CVEs. No entry was seen in the reviewed portion of CISA KEV version 2026.11.20.
- WhatsApp for Android 2.26.35.74 is documented as the fixed build for CVE-2026-102769. CVE-2026-23871 is fixed from 2.26.17.4 and CVE-2026-44908 from the per-platform builds listed in the advisory.
- NVD (source cve-assign@fb.com) publishes all three CVE records: CVE-2026-102769 CVSS 6.8 MEDIUM (CWE-89), CVE-2026-44908 4.8 MEDIUM (CWE-296), CVE-2026-23871 3.5 LOW (CWE-918).
- NVD record modified with CWE-918 (SSRF) secondary weakness mapping for CVE-2026-23871.
- NVD publishes CVE-2026-23871 (status Received) with a CNA-supplied CVSS v3.1 score of 3.5 LOW (AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N) and affected range 2.20.198.3 up to before 2.26.17.4.
- WhatsApp states no evidence of in-the-wild exploitation for CVE-2026-102769 and, per binary transparency ledger data, none for CVE-2026-44908.
- SecurityWeek reports that WhatsApp found CVE-2026-23871 while disrupting a scam campaign and believes a scammer used it to make scam messages seem more credible.
- WhatsApp's November update of its 2026 security advisories lists CVE-2026-23871, CVE-2026-102769 and CVE-2026-44908; CVE-2026-23871 is noted as possibly abused with specific spam messages.
- GBHackers reports that the WhatsApp flaw lets attackers delete files and leak chat database information on Android.
Update history
- 2026-11-21 — WhatsApp Android SQL Injection Flaw (CVE-2026-102769) Enables File Deletion and Chat Database Leak; Plus CVE-2026-44908 and CVE-2026-23871: What changed CVSS 3.5 → 6.8 and severity LOW → MEDIUM. The earlier rating reflected only the headline CVE-2026-23871.
- 2026-11-20 — CVE-2026-23871: WhatsApp Click to WhatsApp ad-reply URL validation flaw (IP disclosure) abused in scam campaign: What changed Severity unchanged (LOW). CVSS score filled in: null → 3.5 (CVSS v3.1, CNA-supplied via NVD). Exploitability, status and attribution unchanged. New indicators (2) Indicator values are withheld at this access level.
Sources cited
- WhatsApp Security Advisories 2026 whatsapp.com · Advisory
- What we learned about TEE security from auditing WhatsApp's Private Inference (Trail of Bits) blog.trailofbits.com · Research · 2026-04-07
- Building Private Processing for AI tools on WhatsApp (Meta Engineering) engineering.fb.com · Vendor report · 2025-04-29
- Meta Private Processing technical whitepaper ai.meta.com · Vendor report
- Update WhatsApp now: two new flaws could expose you to malicious files (Malwarebytes, May 2026 advisory update) malwarebytes.com · Blog
- WhatsApp Fixes Flaw Uncovered While Disrupting Scam Campaign (SecurityWeek) SecurityWeek · News · 2026-11-20
- WhatsApp Private Inference pre-launch audit uncovered critical flaws (CyberInsider) cyberinsider.com · News
Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated .