Skip to main content

WhatsApp for iOS and Android CVE-2026-23866

| EUVDEUVD-2026-26666 MEDIUM
Improper Verification of Source of a Communication Channel (CWE-940)
2026-05-01 cve-assign@fb.com
4.3
CVSS 3.1 · Vendor: fb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker obtains WhatsApp account
  2. Delivery
    Crafts Reels AI response with malicious URL
  3. Exploit
    Sends message to victim
  4. Execution
    Victim device receives and processes message
  5. Persist
    URL scheme handler invoked on OS
  6. Impact
    Limited information disclosed via handler response

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Communication channel verification
Exploitation Conditions

Exploitation requires the attacker to have a valid, authenticated WhatsApp account (PR:L) and for the victim to receive and process the malicious Reels-related AI rich response message. The message must be crafted to leverage the incomplete validation in the specific AI rich response message parser for Reels content, which is a non-default but enabled-by-default feature in the affected versions. The vulnerability does not require the victim to click or interact with the message beyond standard message processing. The attacker cannot exploit this against a user who has not updated to an affected version (versions prior to 2.25.8.0 are not vulnerable) or has already patched beyond the fixed versions. Exploitation is further limited to information that can be disclosed through OS-level URL scheme invocation - arbitrary code execution or full system compromise is not possible.

Impact

Despite a network attack vector (AV:N), this vulnerability presents moderate real-world risk with significant limiting factors. CVSS 4.3 reflects a low-impact information disclosure (C:L, I:N, A:N) with authenticated access required (PR:L), placing it in the low-severity category. CISA SSVC assessment further downgrades priority: exploitation is marked 'none' (no known active attacks), automation is limited by requirement for targeted message delivery and user context, and technical impact is 'partial' (affecting only confidentiality of limited data). The lack of any integrity or availability impact means attackers cannot modify data, cause denial of service, or achieve code execution. However, the combination of network vector with low complexity (AC:L) means an attacker with a valid WhatsApp account can craft and send malicious messages to multiple users without special conditions. The information disclosed via URL scheme invocation is constrained by OS-level access controls and the user's installed apps. The discrepancy between network vector and 'none' exploitation status in SSVC suggests this requires very specific conditions (user receiving and processing the message) that do not occur at scale in typical deployments.

Exploit ScenarioDerived

An authenticated attacker with a valid WhatsApp account crafts an Instagram Reels-related AI rich response message containing a malicious URL designed to trigger a custom URL scheme handler (e.g., 'file://', 'tel://', or a third-party app scheme). When the target user receives and processes the message in WhatsApp, the embedded URL is resolved, invoking the corresponding OS handler and potentially disclosing limited information accessible through that handler. For example, a crafted URL might trigger the iOS Stocks app or an Android banking app to reveal installed app information or trigger unintended actions.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 01, 2026

Incomplete validation of AI rich response messages for Instagram Reels in WhatsApp for iOS v2.25.8.0 through v2.26.15.72 and Android v2.25.8.0 through v2.26.7.10 allows authenticated attackers to trigger processing of media content from arbitrary URLs on a victim's device, potentially invoking OS-controlled custom URL scheme handlers to disclose limited information. No active exploitation has been observed in the wild, and CISA SSVC indicates no known exploitation path despite the network attack vector.

RemediationAI

Users should immediately update to WhatsApp for iOS version 2.26.15.73 or later and WhatsApp for Android version 2.26.7.11 or later, which contain the vendor-released patch addressing incomplete message validation. Updates are available through the Apple App Store and Google Play Store respectively. During the patching process, users can reduce exposure by avoiding clicking on suspicious media content in Reels-related messages from untrusted senders and disabling rich message previews if such an option is available in their WhatsApp settings. Organizations managing WhatsApp for Business should prioritize updates to the same patched versions. No compensating controls can fully mitigate this vulnerability short of disabling AI rich response features; the patch is the recommended remediation path.

Affected VersionsENISA

WhatsApp for Android 2.25.8.0 <2.26.7.10
WhatsApp for iOS 2.25.8.0 <2.26.15.72

Affected Packages

euvd whatsapp_for_android fix: 2.26.7.10
euvd whatsapp_for_ios fix: 2.26.15.72

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability stems from incomplete input validation (CWE-940: Improper Validation of Untrusted Input) in the AI rich response message processing pipeline specific to Instagram Reels integration. When WhatsApp's AI-powered rich message feature processes responses associated with Reels, it fails to adequately sanitize or validate URLs embedded in these messages before triggering media processing. This allows an attacker to inject arbitrary URLs that the victim's device will attempt to resolve, potentially through OS-level URL scheme handlers (such as custom protocols on iOS or Android intent schemes). The vulnerability requires prior authentication and user interaction context (receiving a message), limiting but not eliminating exploitability. The affected versions represent a specific feature implementation window where this validation gap existed.

Know when Whatsapp gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (fb) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Primary rating from Vendor (fb) · only source for this CVE.

CVSS VectorVendor: fb

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

4
Patch released
May 04, 2026 - 15:21 nvd
Patch available
CVSS changed
May 01, 2026 - 17:22 NVD
4.3 (MEDIUM)
Patch available
May 01, 2026 - 17:03 EUVD
CVE Published
May 01, 2026 - 16:16 nvd
MEDIUM 4.3

DescriptionCVE.org

Incomplete validation of AI rich response messages for Instagram Reels in WhatsApp for iOS v2.25.8.0 to v2.26.15.72 and WhatsApp for Android v2.25.8.0 to v2.26.7.10 could have allowed a user to trigger processing of media content from an arbitrary URL on another user’s device, including triggering OS-controlled custom URL scheme handlers. We have not seen evidence of exploitation in the wild.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2025-55177 MEDIUM
5.4 Aug 29

Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Bu

CVE-2022-36934 CRITICAL POC
9.8 Sep 22

An integer overflow in WhatsApp could result in remote code execution in an established video call. Rated critical sever

CVE-2019-11932 HIGH POC
8.8 Oct 03

A double free vulnerability in the DDGifSlurp function in decoding.c in the android-gif-drawable library before version

CVE-2022-27492 HIGH POC
7.8 Sep 23

An integer underflow in WhatsApp could have caused remote code execution when receiving a crafted video file. Rated high

CVE-2018-6344 HIGH POC
7.5 Dec 31

A heap corruption in WhatsApp can be caused by a malformed RTP packet being sent after a call is established. Rated high

CVE-2020-1889 CRITICAL
10.0 Sep 03

A security feature bypass issue in WhatsApp Desktop versions prior to v0.3.4932 could have allowed for sandbox escape in

CVE-2021-24041 CRITICAL
9.8 Dec 07

A missing bounds check in image blurring code prior to WhatsApp for Android v2.21.22.7 and WhatsApp Business for Android

CVE-2021-24026 CRITICAL
9.8 Apr 06

A missing bounds check within the audio decoding pipeline for WhatsApp calls in WhatsApp for Android prior to v2.21.3, W

CVE-2020-1909 CRITICAL
9.8 Nov 03

A use-after-free in a logging library in WhatsApp for iOS prior to v2.20.111 and WhatsApp Business for iOS prior to v2.2

CVE-2020-1907 CRITICAL
9.8 Oct 06

A stack overflow in WhatsApp for Android prior to v2.20.196.16, WhatsApp Business for Android prior to v2.20.196.12, Wha

CVE-2020-1891 CRITICAL
9.8 Sep 03

A user controlled parameter used in video call in WhatsApp for Android prior to v2.20.17, WhatsApp Business for Android

CVE-2019-11933 CRITICAL
9.8 Oct 23

A heap buffer overflow bug in libpl_droidsonroids_gif before 1.2.19, as used in WhatsApp for Android before version 2.19

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy