WhatsApp: verify updates for each app and device
An update confirmation should identify the application, platform and devices it covers. WhatsApp’s advisories help organize that decision while keeping patch acceptance and fraud investigation separate.
Ler em portuguêsBy Pentesty
Start with the differences between the advisories
Records published on November 20, 2026 describe different conditions. CVE-2026-23871 concerns IP exposure through ad replies in Android and Business Android before 2.26.17.4, with possible spam-related abuse. CVE-2026-102769 can delete local files and cause a limited timing leak; the CNA lists Android and Business Android before 2.26.35.74, without observed exploitation.
CVE-2026-44908 concerns attestation for the AI backend, requires a position within Meta infrastructure and has product-specific version thresholds. Meta says the transparency record confirms no exploitation in that case.
This set calls for an update decision for each application. Avoid treating the service’s commercial name as a single inventory entry. The team needs to distinguish the products in use, their installation sources and the devices for which it has enough information to accept the update. That distinction also makes it easier to assign the change to an owner.
Make the inventory answer a practical question
Start with the groups using messaging for company work. Identify who administers their phones and how the application is distributed. For each group, record the platform, installed product, observed version and collection date. Specify who will resolve an incomplete entry. This list should support the update process without collecting conversations, personal contacts or other information unnecessary for deciding whether deployment is complete.
Agree in advance which evidence is acceptable: a corporate management report, a supervised check or another method approved for that environment. Sending an update command still requires confirmation of its outcome. Track powered-off, unavailable and unmanaged devices separately. Give these exceptions an owner and a deadline, so a compliance average does not conceal a device that retains important access.
Connect deployment to permitted use
After the change, confirm the required functions with test accounts and messages. A sales team may need to validate customer service, while another group depends on document exchange or an approved integration. Choose a sample representing those differences and record the expected result before testing. Acceptance should show that deployment reached the devices and that authorized work remains possible under the agreed conditions.
When a device’s status remains unknown, make an explicit decision about corporate access. The service owner should assess the need for continued use alongside the controls available. Pair any restriction with an operational alternative and a support route. The distinction between system updates and application updates also informs our analysis of Android patch evidence, which addresses another part of the device’s maintenance record.
Keep message investigation in its own process
If someone reports a suspicious message, preserve the necessary context and refer the case to incident response. Record when the report arrived, which account was involved and which actions the person remembers taking. Do not ask them to repeat an interaction to demonstrate the problem. The response team should define collection requirements and decide whether available signs justify expanding the investigation.
Completing an update and completing an investigation require different evidence. Present the two outcomes separately to management, with remaining tasks and owners. Reviewing computers linked to messaging accounts helps organize another access decision when it falls within scope. Closure should state what was checked, which population the evidence covers and when a further review will become necessary, allowing another person to understand the decision later.
Frequently asked questions
Which version belongs in the report?
Record the observed version of the installed product, together with its platform and date. Compare it with the relevant advisory instead of treating one number as a universal requirement for every device.
Does sending the update close the task?
Acceptance needs confirmation of the outcome and a record of exceptions. A device that does not respond should remain visible in the follow-up, with someone responsible for the next action.
Must conversations be exported to verify the fix?
A version check should use evidence proportionate to that purpose. Collecting material to investigate a message needs a separate scope, defined by the responsible team and limited to what is necessary.
Who approves an exception for continued use?
The service owner should decide with access owners and security. Record the justification, the available alternative and the condition that will trigger a review of the decision.
Sources and references
- Meta and CVE Program: CVE-2026-23871
- Meta and CVE Program: CVE-2026-102769
- Meta and CVE Program: CVE-2026-44908
Original Pentesty analysis, published November 20, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.