How severe is GHSA-qvv5-jq5g-4cgg?

No CVSS score has been assigned to GHSA-qvv5-jq5g-4cgg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qvv5-jq5g-4cgg?

GHSA-qvv5-jq5g-4cgg affects the following packages: baileys (npm), @whiskeysockets/baileys (npm), baileys (npm), @whiskeysockets/baileys (npm). Ecosystems affected: npm.

How do I fix GHSA-qvv5-jq5g-4cgg?

Update baileys to 6.7.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvv5-jq5g-4cgg is resolved across your whole dependency graph.

How do I detect GHSA-qvv5-jq5g-4cgg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baileys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qvv5-jq5g-4cgg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qvv5-jq5g-4cgg actively exploited in the wild?

No public exploit code has been indexed for GHSA-qvv5-jq5g-4cgg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qvv5-jq5g-4cgg?

GHSA-qvv5-jq5g-4cgg has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qvv5-jq5g-4cgg?

GHSA-qvv5-jq5g-4cgg is classified as CWE-290 (CWE-290), CWE-345 (CWE-345), CWE-346 (CWE-346). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qvv5-jq5g-4cgg published, and has it been updated?

GHSA-qvv5-jq5g-4cgg was published on June 10, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payloadGHSA-qvv5-jq5g-4cgg

Fix: WhiskeySockets/Baileys@3beb08e

GHSA-qvv5-jq5g-4cgg is a CWE-290 vulnerability in baileys. A fix is available for baileys — see the affected versions and patch details below.

Also known asCVE-2026-48063

Published

Jun 10, 2026

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qvv5-jq5g-4cgg.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

135other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

baileysnpm

235Kdownloads / week

@whiskeysockets/baileysnpm

307Kdownloads / week

Description

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`baileys`	all versions	6.7.22`npm install baileys@6.7.22`
📦npm	`@whiskeysockets/baileys`	all versions	6.7.22`npm install @whiskeysockets/baileys@6.7.22`
📦npm	`baileys`	≥ 7.0.0-rc.1&&< 7.0.0-rc12	7.0.0-rc12`npm install baileys@7.0.0-rc12`
📦npm	`@whiskeysockets/baileys`	≥ 7.0.0-rc.1&&< 7.0.0-rc12	7.0.0-rc12`npm install @whiskeysockets/baileys@7.0.0-rc12`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for baileys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update baileys to 6.7.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvv5-jq5g-4cgg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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/3beb08eecfcb4e65722e674034bd8

O3 Security · Impact-Aware SCA

Is GHSA-qvv5-jq5g-4cgg in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works