Skip to main content
Menu
CVEs

Facebook WhatsApp Business for Android IP address leak via incomplete ad-reply URL validation

CVE-2026-23871Published , updated

3.5LowCNA
Exploited
No known exploitation
Fix
Fixed in 2.26.17.4
Who is exposed
Not reported

Summary

Incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android could let an attacker learn a target's device IP address. The attacker can reach it remotely over the network by sending a crafted Click to WhatsApp ad-reply message that loads media from an attacker-controlled URL, and the attack works once the target's device renders and displays that message in a chat thread.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 2.26.17.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-23871 (Incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4 could have…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-23871 (entry last updated 2026-11-20):
Affected:
- Facebook WhatsApp Business for Android: from 2.20.198.3, fixed in 2.26.17.4
- Facebook WhatsApp for Android: from 2.20.198.3, fixed in 2.26.17.4
Fixed versions: 2.26.17.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-23871 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-23871 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.facebook.com/security/advisories/cve-2026-23871
- https://www.whatsapp.com/security/advisories/2026
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-23871
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-23871"}.

Affected versions

cve.now Index

7Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity3.5/10CVSS 3.5
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. cve.now early warning

    WhatsApp fixes Android flaw CVE-2026-23871 that it believes a scammer used

  3. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
Linkfacebook.com · security/advisories/cve-2026-23871
Linkwhatsapp.com · security/advisories/2026
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-23871
RecordNVD · CVE-2026-23871

Questions about CVE-2026-23871

Is CVE-2026-23871 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-23871?

WhatsApp Business for Android: from 2.20.198.3 before 2.26.17.4. WhatsApp for Android: from 2.20.198.3 before 2.26.17.4.

Source: cve.now feed data

How do I fix CVE-2026-23871?

Upgrade to a fixed version: 2.26.17.4.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.