Loading...
Skip to main content
GeekWala

CVE-2026-48063 — Vulnerability in baileys — CVE Details

CRITICAL

Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payload

Published June 10, 2026Updated September 10, 2026Source: osv

Summary

### 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. ### Patches 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. ### 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.

Advisory Timeline

  • First published June 10, 2026 (124 days ago).
  • Last revised September 10, 2026 — 91 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

npm
Update baileys to 6.7.22 or later
npm install baileys@6.7.22
npm
Update @whiskeysockets/baileys to 6.7.22 or later
npm install @whiskeysockets/baileys@6.7.22
npm
Update baileys to 7.0.0-rc12 or later
npm install baileys@7.0.0-rc12
npm
Update @whiskeysockets/baileys to 7.0.0-rc12 or later
npm install @whiskeysockets/baileys@7.0.0-rc12

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (4)

Affects 1 ecosystem: npm (2).

PackageEcosystemAffectedFixed In
baileys
npm
All versions6.7.22
@whiskeysockets/baileys
npm
All versions6.7.22
baileys
npm
All versions7.0.0-rc12
@whiskeysockets/baileys
npm
All versions7.0.0-rc12

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

References

Frequently Asked Questions

What is CVE-2026-48063?
Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payload This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.1/10).
How do I check if my project is affected by CVE-2026-48063?
CVE-2026-48063 affects baileys and @whiskeysockets/baileys. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-48063 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.1

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-qvv5-jq5g-4cgg

Related CVEs

  • CVE-2026-107722
    CRITICAL

    fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion

  • CVE-2026-108261
    CRITICAL

    TinaCMS admin preview iframe loads an attacker-controlled origin from the URL fragment

More npm advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies