Vulnerability in @openclaw/whatsapp (CVE-2026-100532)
Summary
Vulnerability in @openclaw/whatsapp (CVE-2026-100532). Data can be tampered with by attackers. Mitigation: upgrade to 2026.8.1 or later.
Original description
The description as published by the source.
@openclaw/whatsapp (npm) before 2026.8.1 exposes the WhatsApp login tool through the generic channel-tool path without preserving the originating sender's owner status, so the owner-only tool boundary is not enforced. An admitted non-owner sender able to steer the tool can request a forced login and receive a new QR code for a configured account, disconnecting the Gateway's WhatsApp account and causing loss of availability; full account relinking additionally requires the attacker to scan the returned QR code with another phone. The issue affects the owner-only tool boundary rather than WhatsApp transport authentication. Fixed in 2026.8.1.
Source: NIST National Vulnerability Database 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-100532 has been found in @openclaw/whatsapp.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade @openclaw/whatsapp to 2026.8.1 or later.
If unsure, ask your IT team or search "@openclaw/whatsapp CVE-2026-100532" on the vendor's site.
CVE-2026-100532 (@openclaw/whatsapp) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.8.1 — apply immediately
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.
A vulnerability (CWE-862) exists in @openclaw/whatsapp.
Check the vendor advisory for the affected versions of @openclaw/whatsapp.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 2026.8.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@openclaw/whatsapp' . 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
-
1Identify exposure identify
grep -r '@openclaw/whatsapp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@openclaw/whatsappを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @openclaw/whatsapp to 2026.8.1ステージング環境で 2026.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com