Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48063

Vulnerability in baileys (CVE-2026-48063)

Summary

Vulnerability in baileys (CVE-2026-48063). Risk of unauthorized operations or information disclosure. Exploitable via messages.upsert. Mitigation: upgrade to 7.0.0-rc12 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48063 has been found in baileys.
Attackers can target a specific entry point like messages.upsert over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade baileys to 7.0.0-rc12 or later.
If unsure, ask your IT team or search "baileys CVE-2026-48063" on the vendor's site.

CVE-2026-48063 (baileys) — CWE-290
Attack surface: messages.upsert / requestId
Patched: 7.0.0-rc12 — apply immediately
Workaround: 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.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-290) exists in baileys. Attackers reach the vulnerable code path via messages.upsert.

📍 Affected scope

Check the vendor advisory for the affected versions of baileys. Attack surface: messages.upsert / requestId.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.0.0-rc12.

🛡️ Workaround

Workaround: 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.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'baileys' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'baileys' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で baileys を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    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 real workarounds other than dropping messages.upsert events that contain a requestId field, turning off automatic history sync (shouldSyncHistoryMessage: () => false) in socket config. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade baileys to 7.0.0-rc12

    ステージング環境で 7.0.0-rc12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm baileys
[{"type":"SEMVER","events":[{"introduced":"7.0.0-rc.1"},{"fixed":"7.0.0-rc12"}]}]
npm @whiskeysockets/baileys
[{"type":"SEMVER","events":[{"introduced":"7.0.0-rc.1"},{"fixed":"7.0.0-rc12"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details