Facebook certificate chain bypass in remote attestation verifier
- Exploited
- No known exploitation
- Fix
- 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
- Who is exposed
- Not reported
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
Original 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
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.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
- Facebook WhatsApp Desktop for MacFrom 2.25.17.81 · fixed in 2.26.23.72
- Facebook WhatsApp Business for iOSFrom 2.25.17.81 · fixed in 2.26.23.72
- Facebook WhatsApp for iOSFrom 2.25.17.76 · fixed in 2.26.24.72
- Facebook WhatsApp Business for AndroidFrom 2.25.17.71 · fixed in 2.26.23.70
- Facebook WhatsApp for AndroidFrom 2.25.17.77 · fixed in 2.26.23.74
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- cve.now early warning
WhatsApp fixes Android flaw CVE-2026-23871 that it believes a scammer used
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Link | facebook.com · security/advisories/cve-2026-44908 |
| Link | whatsapp.com · security/advisories/2026 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-44908 |
| Record | NVD · CVE-2026-44908 |
Questions about CVE-2026-44908
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: cve.now feed data
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: cve.now feed data
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: cve.now feed data
Related
- SZB-1915a53049Started as this early warning
- CVE-2021-24042The calling logic for WhatsApp for Android prior to v2.21.23, WhatsApp Business for Android prior to v2.21.23, WhatsApp for iOS prior to v2.
- CVE-2021-24041A missing bounds check in image blurring code prior to WhatsApp for Android v2.21.22.7 and WhatsApp Business for Android v2.21.22.7 could…
- CVE-2021-24026A missing bounds check within the audio decoding pipeline for WhatsApp calls in WhatsApp for Android prior to v2.21.3, WhatsApp Business…
- CVE-2020-1909A use-after-free in a logging library in WhatsApp for iOS prior to v2.20.111 and WhatsApp Business for iOS prior to v2.20.111 could have…
- CVE-2020-1907A stack overflow in WhatsApp for Android prior to v2.20.196.16, WhatsApp Business for Android prior to v2.20.196.12, WhatsApp for iOS…
No corrections so far. Something wrong on this page? Report an error.