Skip to main content
Mallory
MediumVulnerability

CVE-2026-44908: Hardware root-of-trust bypass in WhatsApp remote-attestation verification

Published Nov 20, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 5 in a dayToday
CVSS4.8Medium · v3.1
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-44908CWE-296 · Improper Following of a…

CVE-2026-44908 is an improper certificate-chain validation vulnerability in the remote-attestation verifier used by WhatsApp clients to establish trust with Meta AI's confidential computing backend. An attacker positioned within Meta infrastructure could present a Versioned Chip Endorsement Key (VCEK) certificate signed by a key other than the hardware manufacturer's, bypassing the hardware root of trust. The certificate would first need to be published to the third-party binary transparency ledger used by WhatsApp Private Processing. Affected versions are WhatsApp for iOS before 2.26.24.72; WhatsApp Business for iOS and WhatsApp for Mac Desktop before 2.26.23.72; WhatsApp for Android before 2.26.23.74; and WhatsApp Business for Android before 2.26.23.70. All published VCEK certificates chained to the hardware root of trust, confirming no exploitation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation could undermine the hardware-backed trust guarantees of WhatsApp Private Processing by causing clients to accept an attestation certificate that does not chain to the hardware manufacturer's root of trust. Specific downstream effects, such as data disclosure or code execution, are not established.

Remediation

Patch, then assume compromise.

Upgrade WhatsApp for iOS to 2.26.24.72 or later; WhatsApp Business for iOS and WhatsApp for Mac Desktop to 2.26.23.72 or later; WhatsApp for Android to 2.26.23.74 or later; and WhatsApp Business for Android to 2.26.23.70 or later.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-44908 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-44908 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-44908?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-44908.
Is there a patch for CVE-2026-44908?
Upgrade WhatsApp for iOS to 2.26.24.72 or later; WhatsApp Business for iOS and WhatsApp for Mac Desktop to 2.26.23.72 or later; WhatsApp for Android to 2.26.23.74 or later; and WhatsApp Business for Android to 2.26.23.70 or later.
How severe is CVE-2026-44908?
CVE-2026-44908 has a CVSS v3.1 score of 4.8 (Medium) as of Nov 21, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
security affairsNews · Nov 20, 2026CVE-2026-23871: WhatsApp Bug Helped Scammers Make Messages Look LegitimateA remote-attestation verification flaw could allow an attacker positioned inside Meta’s infrastructure to bypass the hardware root of trust by presenting a certificate signed by an incorrect key. Exploitation would require the certificate to appear on a public transparency ledger. WhatsApp reports that all published certificates validate correctly, with no indication of exploitation. A fix is available, but specific fixed versions are not provided.Read more ↗the hacker newsNews · Nov 20, 2026WhatsApp Patches 3 Security Flaws, Including Android Bug Suspected of Use in ScamsA trust-validation flaw in WhatsApp's certificate verification for Meta AI confidential computing infrastructure could allow an attacker positioned within Meta infrastructure to bypass the hardware root of trust using an improperly signed VCEK certificate. Such a certificate would first need publication in the third-party binary transparency ledger. WhatsApp states that all published certificates chain to the hardware root of trust, confirming no exploitation.Read more ↗security weekNews · Nov 20, 2026WhatsApp Fixes Flaw Uncovered While Disrupting Scam Campaign - SecurityWeekA medium-impact remote-attestation verification flaw could allow someone positioned within Meta infrastructure to bypass the hardware root of trust using a certificate not signed by the hardware manufacturer’s key. It affected certain versions of WhatsApp and WhatsApp Business for Android and iOS, and WhatsApp for Mac. Exploitation would first require publishing the certificate to a third-party binary transparency ledger. WhatsApp said the ledger confirmed that no exploitation occurred.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.