ForgeNEX

WhatsApp fixes three flaws: the Android one has already been used in scams

Meta patches three vulnerabilities in WhatsApp, one of them on Android linked to fraudulent messages. Key steps to protect your SMB's phones.

3 min read

In this article

WhatsApp has made its move. Meta has published fixes for three security vulnerabilities in its messaging app, and one of them deserves special attention in any SMB that uses mobile phones as a work tool: a flaw in the Android version that the company suspects may have been exploited in scam campaigns.

The issue, registered as CVE-2026-23871 with a CVSS score of 3.5, affects WhatsApp for Android and WhatsApp Business for Android in versions prior to 2.26.17.4. The technical description refers to incomplete validation of external ad reply URLs. Translated into plain language: the app did not fully check the links generated when a user interacts with an ad inside the platform, and that opens the door for an attacker to manipulate that flow.

Why a low score does not mean low risk

A CVSS of 3.5 is classified as low severity, and IT teams often file it away without further thought. Mistake. That score measures the technical impact of the flaw in isolation, not the context. And the context here is that WhatsApp Business is, for many SMBs, the main channel for customer service, quotes and orders. A manipulated link that arrives through a route the user perceives as legitimate — an ad inside the app itself — is prime material for phishing.

The suspicion of exploitation in scams is the part that should concern us: we are not talking about a theoretical laboratory flaw, but about something Meta links to real fraud attempts.

It is worth remembering that the messaging scam ecosystem has been growing more sophisticated for some time. We have already discussed this in this blog when talking about how social engineering evolves with AI and malware disguised in images. The pattern repeats: the attacker does not need to break encryption; it is enough for the user to click where they should not.

Illustrative detail: WhatsApp Patches 3 Security Flaws, Including Android Bug Suspected of Use in Scams

What your team should do this very week

The good news is that mitigation is simple and requires no budget. These are the actions we recommend at ForgeNEX:

  1. Update WhatsApp and WhatsApp Business on all company Android devices. Check in Settings that the installed version is 2.26.17.4 or higher. Do not wait for the update to arrive on its own: on managed devices, force the check from the app store.
  2. Review the team's personal phones. BYOD is the norm in many SMBs. A personal device with an outdated app used to reply to customers is a textbook corporate risk.
  3. Reinforce training on one specific point: be suspicious of links that arrive after interacting with an ad, even if the sender appears to be WhatsApp or a known provider. Always verify through an alternative channel before entering credentials or bank details.
  4. Document the incident if you suspect one. If someone on the team clicked on something strange, do not let it go: change passwords, review recent access and, if customer data has been compromised, activate the internal protocol.

The phone as the perimeter: a recurring lesson

This episode fits a trend we have been observing. Patches for messaging apps are no longer a domestic matter. When the phone is the office, the attack surface multiplies and update deadlines get shorter. It is the same logic we apply when we warn about a critical flaw with active attacks: the window between publication of the patch and mass exploitation is measured in days, sometimes hours.

For an SMB without a dedicated security department, the practical recommendation is to build a routine: a fixed day each month to review updates for critical apps on all devices, a minimal inventory of which devices access which data, and a clear policy that phones with access to customer information must be updated without exceptions. You do not need a SOC for that; you need consistency.

Meta has fixed the three flaws, but the patch only protects those who install it. In security, the difference between a calm SMB and an SMB with an incident is usually five minutes and an ignored update notification.

Source: The Hacker News. Analysis and adaptation: ForgeNEX.

Keep reading

Call us WhatsApp