On 1 May 2026, Facebook, Inc. published CVE-2026-23866 on its security advisories site. The description, quoted here only in substance, is that incomplete validation of AI rich-response messages for Instagram Reels in WhatsApp for iOS versions 2.25.8.0 through 2.26.15.72 and WhatsApp for Android versions 2.25.8.0 through 2.26.7.10 could have allowed a user to trigger processing of media from an arbitrary URL on another user’s device, including OS-controlled custom URL scheme handlers. Meta stated: “We have not seen evidence of exploitation in the wild.” Affected-version lines on the same page mark Android 2.25.8.0 before 2.26.7.10 and iOS 2.25.8.0 before 2.26.15.72 as affected, with default status unaffected outside those ranges.
That bug sits next to an earlier, related advisory. CVE-2025-55179, also published by Facebook, describes incomplete validation of rich-response messages in WhatsApp for iOS prior to 2.25.23.73, WhatsApp Business for iOS prior to 2.25.23.82, and WhatsApp for Mac prior to 2.25.23.83. The impact language is the same family of issue: a user could trigger another device to process media from an arbitrary URL. Again Meta wrote that it had not seen exploitation in the wild. The 2025 advisory’s affected ranges start at 2.25.8.14 or 2.25.8.17 depending on the product line.
Neither advisory, in the text loaded for this briefing, assigns a CVSS score on Meta’s page. They do not name a researcher, a proof-of-concept, or a specific URL scheme that would have launched. They do not claim remote code execution, data theft, or account takeover. The realistic reading of Meta’s words is a cross-user content-processing bug: if you were in a position to send a crafted rich response, you might cause someone else’s WhatsApp to fetch a URL you chose, and on some operating systems that fetch can invoke a handler registered by another app. Whether that is a nuisance, a phishing trampoline, or a stepping stone depends on what handlers are installed. Meta does not enumerate them.
The Instagram Reels and “AI rich response” phrasing in CVE-2026-23866 is important for operators. It suggests the vulnerable parser was not the ordinary image bubble but a richer card used when WhatsApp surfaces Reel-related or AI-assisted responses. Users who never interact with those surfaces were not thereby proven safe; parsers often run on receipt. Meta’s version numbers are the only patch map this briefing uses. Anyone still on a build older than the “before” versions listed should update from the official store. Sideloaded or outdated APKs are outside Meta’s stated fixed range.
A third WhatsApp issue, CVE-2026-23863, appears in public CVE indexes as a Windows attachment-spoofing bug involving NUL bytes in filenames, with Meta again stating no evidence of in-the-wild exploitation. This briefing does not treat that CVE as confirmed from a loaded vendor page; the Facebook advisory URLs that did load for this item are 2026-23866 and 2025-55179 only.
What this means in practice
Update WhatsApp, WhatsApp Business, and WhatsApp Desktop from official stores until the installed version is newer than the ranges Meta listed. Treat unsolicited rich cards, Reel previews, and AI response bubbles as potentially untrusted content even after patching, because that is how the feature is designed. Do not rely on “I only chat with family” as a control: the advisories describe another WhatsApp user as the sender. Organisations that manage phones should inventory versions rather than assume auto-update ran. Cyber71 cannot obtain a hotfix from Meta, confirm whether a given number was targeted, or restore a compromised phone.
What is still unclear
Meta’s “no evidence of exploitation” statement is an internal observation, not a proof of absence. The NVD HTML pages for these CVEs did not return usable detail when fetched for this workstream, so scoring, CWE, and CPE lines from NVD are not quoted here. How the iOS and Android URL-handler paths differ, whether WhatsApp Business for Android shared the 2026 bug, and whether Instagram’s own app was affected are not answered on the two advisory pages loaded. Patch completeness across WhatsApp Web is also not stated there.
Sources
- Facebook Security Advisories — CVE-2026-238662026-09-24
- Facebook Security Advisories — CVE-2025-551792026-09-24
Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.
