Summary
Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payload
Workarounds
There are no real workarounds other than dropping messages.upsert events that contain a requestId field, turning off automatic history sync (shouldSyncHistoryMessage: () => false) in socket config. There are no workarounds for the app state sync jamming.
Impact
Any baileys session under the latest version (< 7.0.0-rc12, and < 6.7.22) can be sent a malicious payload via the placeholderResendMessage and trigger a fake messages.upsert event with a fake message key and payload. This allows anyone to spoof messages. The same exploit also allows an attacker to corrupt the app state sync system by sending fake key shares, and also allows for history sync spoofing which also serves the same problem, injecting fake previous context or "on-demand" sync.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
https://github.com/WhiskeySockets/Baileys/commit/3beb08eecfcb4e65722e674034bd84fb11a9de35 This commit has patched the issue, and a version tag has been released under 7.0.0 (6.7.22) for those still on Baileys v6. A new Baileys version, v7.0.0-rc12, has been released to remediate this.
Frequently Asked Questions
- What is CVE-2026-48063? CVE-2026-48063 is a critical-severity security vulnerability in baileys (npm), affecting versions < 6.7.22. It is fixed in 6.7.22, 7.0.0-rc12.
- Which packages are affected by CVE-2026-48063?
baileys(npm) (versions < 6.7.22)@whiskeysockets/baileys(npm) (versions < 6.7.22)
- Is there a fix for CVE-2026-48063? Yes. CVE-2026-48063 is fixed in 6.7.22, 7.0.0-rc12. Upgrade to this version or later.
- Is CVE-2026-48063 exploitable, and should I be worried? Whether CVE-2026-48063 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-48063 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-48063?
- Upgrade
baileysto 6.7.22 or later - Upgrade
@whiskeysockets/baileysto 6.7.22 or later - Upgrade
baileysto 7.0.0-rc12 or later - Upgrade
@whiskeysockets/baileysto 7.0.0-rc12 or later
- Upgrade