CVE-2026-48063
Remote message spoofing and state-sync corruption in Baileys (WhatsApp Web client).
Is CVE-2026-48063 being exploited?
Not confirmed. CVE-2026-48063 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-48063?
CVE-2026-48063 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48063?
Yes. A fix has been recorded for CVE-2026-48063. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48063 affect?
CVE-2026-48063 affects Baileys (WhatsApp Web JS/TS) versions < 6.7.22, Baileys versions < 7.0.0-rc12, Applications/services using Baileys for WhatsApp automation/integration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48063?
Upgrade to 6.7.22 or 7.0.0-rc12; rotate session keys; audit integrations and message handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can spoof messages, inject fake history and key shares, and corrupt state sync to mislead users or alter app context.
Immediate action required
- affected< 6.7.22
- affected>= 7.0.0-rc.1 and < 7.0.0-rc12
- affected< 6.7.22
- affected>= 7.0.0-rc.1 and < 7.0.0-rc12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.