CVE-2026-48063: Baileys Baileys Has Message Upsert / Vulnerability

CRITICAL
Advisory Identifier: GHSA-qvv5-jq5g-4cgg
Share
CWE-345 CWE-346 CWE-290
Published
Advisory Summary

CVE-2026-48063 is a CRITICAL baileys has message upsert / vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Baileys libraries in the npm ecosystem. The issue involves baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolmessage payload. Remediation is available by upgrading affected packages to version 6.7.22, 7.0.0-rc12.

CVE-2026-48063 at a Glance

CVE Identifier CVE-2026-48063
GHSA Identifier GHSA-qvv5-jq5g-4cgg
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product Baileys
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-48063

To remediate this vulnerability, upgrade all affected Baileys dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

baileys fixed: 6.7.22 
npm install baileys@6.7.22
@whiskeysockets/baileys fixed: 6.7.22 
npm install @whiskeysockets/baileys@6.7.22
baileys fixed: 7.0.0-rc12 
npm install baileys@7.0.0-rc12
@whiskeysockets/baileys fixed: 7.0.0-rc12 
npm install @whiskeysockets/baileys@7.0.0-rc12
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls baileys

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-48063, inspect your project dependencies using npm:

npm ls baileys

Analyze the terminal output to locate any version of Baileys in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.7.22), your application is affected.

Note: The npm ls baileys command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Baileys, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-48063 Affected Baileys Versions

4 component(s)
Fixed Versions:
6.7.227.0.0-rc12
Product / Package Ecosystem Affected Versions Fixed Version
baileys
npm/baileys
npm
< 6.7.22
6.7.22
@whiskeysockets/baileys
npm/@whiskeysockets/baileys
npm
< 6.7.22
6.7.22
baileys
npm/baileys
npm
≥ 7.0.0-rc.1
< 7.0.0-rc12
7.0.0-rc12
@whiskeysockets/baileys
npm/@whiskeysockets/baileys
npm
≥ 7.0.0-rc.1
< 7.0.0-rc12
7.0.0-rc12

References

GitHub Advisory / Wiki ADVISORY
https://github.com/WhiskeySockets/Baileys/security/advisories/GHSA-qvv5-jq5g-4cgg
Security Fix Commit FIX COMMIT
https://github.com/WhiskeySockets/Baileys/commit/3beb08eecfcb4e65722e674034bd84fb11a9de35
Baileys Source Repository REPOSITORY
https://github.com/WhiskeySockets/Baileys

Frequently Asked Questions

What is CVE-2026-48063?
CVE-2026-48063 is a security vulnerability in Baileys involving Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payload under CWE-345: Insufficient Verification of Data Authenticity.
Which Baileys versions are affected?
Affected versions include releases prior to 6.7.22, 7.0.0-rc12 across affected packages: baileys, @whiskeysockets/baileys.
What version fixes CVE-2026-48063?
Upgrading to 6.7.22, 7.0.0-rc12 (or the latest patched release for your respective branch) resolves the vulnerability.
Is baileys affected?
Yes, baileys is affected in releases prior to 6.7.22, 7.0.0-rc12. Upgrade your dependency to 6.7.22, 7.0.0-rc12 or later.
Is @whiskeysockets/baileys affected?
Yes, @whiskeysockets/baileys is affected in releases prior to 6.7.22, 7.0.0-rc12. Upgrade your dependency to 6.7.22, 7.0.0-rc12 or later.
What CWE is associated with CVE-2026-48063?
CVE-2026-48063 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check npm dependencies for CVE-2026-48063?
Run the dependency tree command: 'npm ls baileys'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qvv5-jq5g-4cgg",
  "modified" : "2026-06-10T19:33:20Z",
  "published" : "2026-06-10T19:33:20Z",
  "aliases" : [ "CVE-2026-48063" ],
  "summary" : "Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payload",
  "details" : "### Impact\nAny 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.\n\n### Patches\nhttps://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.\n\n\n### Workarounds\nThere 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.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "baileys"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.7.22"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@whiskeysockets/baileys"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.7.22"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "baileys"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.0-rc.1"
      }, {
        "fixed" : "7.0.0-rc12"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@whiskeysockets/baileys"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.0-rc.1"
      }, {
        "fixed" : "7.0.0-rc12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WhiskeySockets/Baileys/security/advisories/GHSA-qvv5-jq5g-4cgg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WhiskeySockets/Baileys/commit/3beb08eecfcb4e65722e674034bd84fb11a9de35"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WhiskeySockets/Baileys"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-290", "CWE-345", "CWE-346" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-10T19:33:20Z",
    "nvd_published_at" : null
  }
}