WhatsApp patches 3 flaws, one Android bug tied to scam messages
WhatsApp fixed three flaws, including CVE-2026-23871, an Android bug its security team found and says a scammer abused to make scam messages look more credible. Fixed in 2.26.17.4.
WhatsApp patched three security flaws, disclosed in its November 2026 advisories. The notable one is an Android bug WhatsApp's own security team found while disrupting a scam campaign — and which it believes a scammer was already abusing. None is a wormable pre-auth RCE, but if you own mobile fleet policy, confirm your minimum enforced WhatsApp version covers the fixes.
The flaws
- CVE-2026-23871 (low) — the Android bug tied to Click to WhatsApp ads. Affects WhatsApp and WhatsApp Business for Android before 2.26.17.4; fixed in 2.26.17.4. WhatsApp says it "may have been abused in conjunction with specific spam messages," and a spokesperson said "we believe a scammer was using it to make their scam message seem more credible."
- CVE-2026-102769 (medium) — a SQL injection in WhatsApp for Android prior to 2.26.35.74; fixed in 2.26.35.74. Reported by an external researcher through Meta's bug-bounty program.
- CVE-2026-44908 (medium) — a remote-attestation verifier flaw affecting certain versions of WhatsApp and WhatsApp Business for iOS and Android, and WhatsApp for Mac. Discovered by Meta's own researchers.
Exploitation status
The only flaw WhatsApp links to real abuse is CVE-2026-23871, and it frames that carefully: found internally during a scam-campaign takedown, with the company stating its belief that a scammer leveraged it to lend credibility to spam rather than to achieve code execution or account takeover. WhatsApp says it has seen no evidence that CVE-2026-102769 or CVE-2026-44908 was exploited. For CVE-2026-44908, WhatsApp notes a certificate could not have been used without first being published to a third-party binary-transparency ledger — a meaningful constraint on practical abuse.
Action checklist
- Ensure WhatsApp and WhatsApp Business for Android are at 2.26.17.4 or later to close CVE-2026-23871, and at 2.26.35.74 or later for the SQL-injection fix.
- In MDM-managed fleets, raise the minimum enforced version and push the update rather than relying on auto-update timing.
- For the attestation flaw (CVE-2026-44908), make sure iOS, Android and Mac clients are on the current release once the fixed build is published.
- Brief fraud and support teams: the Android bug was about making scam messages look more trustworthy, so the user-facing risk is social-engineering, not device compromise.
Context
This is a self-disclosed, low-to-medium-severity batch — the kind vendors ship routinely — but the detail worth keeping is how CVE-2026-23871 surfaced: not from a researcher report, but from WhatsApp hunting a scam operation and finding the abused flaw in the process. That is the healthier failure mode. The takeaway for practitioners is mundane but real: version-enforce messaging apps the same way you version-enforce browsers, because "a scammer used it to look more credible" is exactly the kind of abuse that never generates a CVSS 9 but still lands in your users' inboxes.