CVE-2026-44908

WhatsApp Private Processing attestation could trust the wrong certificate chain

Facebook · Meta AI · WhatsApp Private Processing

First documented disclosure · Review checkpoint

Summary

A positioned attacker could bypass the hardware-root check used to establish trust with the AI confidential-computing backend.

Severity and exploitation evidence

Medium · 4.8/10 · CVSS 3.1. Severity source.

Exploitation not established: Meta says every certificate in the required transparency ledger chains to the hardware root, confirming no exploitation of this issue. This is the vendor’s conclusion; the ledger was not independently audited here.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The attestation verifier could accept a VCEK certificate signed by a key other than the hardware manufacturer’s.

Conditions required

A position within Meta infrastructure and prior publication of the rogue certificate to the third-party binary-transparency ledger; the vendor CVSS vector additionally requires high privileges and user interaction.

Potential impact

Loss of the intended hardware-root-of-trust guarantee, with confidentiality and limited integrity impact.

Affected versions and configurations

Mac Desktop and Business iOS: 2.25.17.81 to before 2.26.23.72; iOS: 2.25.17.76 to before 2.26.24.72; Business Android: 2.25.17.71 to before 2.26.23.70; Android: 2.25.17.77 to before 2.26.23.74.

Fix and mitigation status

Mac Desktop / Business iOS 2.26.23.72; iOS 2.26.24.72; Business Android 2.26.23.70; Android 2.26.23.74.

Practical next steps

Update the relevant WhatsApp application to its corrected platform build.

Operating lesson

Verify attestation chains against the intended hardware root and retain externally auditable certificate transparency.

Evidence and limits

Exact CNA initial publication 16: 00: 40.504Z is inside the review cutoff. A later 16: 16: 25Z record update adds CISA enrichment without changing the CNA; that enrichment is not treated as an in-interval development. The first reviewed issue-specific public date is November 20; a release date for each corrected app build is not established. The manufacturer’s exploitation conclusion is grounded in its inspection of the transparency ledger, not an independent review of that ledger here. CNA publication is 2026-11-20; this is distinct from the earliest reviewed public source and correction dates. Meta assessments: CVSS 3.1 4.8.

Sources