CVE-2026-62196
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw versions 2026.3.22 before 2026.6.6 contain an authorization bypass vulnerability where WhatsApp group IDs can satisfy elevated sender allowlists. Attackers with lower-trust access can perform actions requiring stronger authorization by leveraging group ID validation in the affected feature.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenClaw versions 2026.3.22 through 2026.6.5 contain an authorization bypass where WhatsApp group IDs are incorrectly validated against elevated sender allowlists that should only permit individual high-privilege users. Attackers with lower-trust access can exploit this by sending messages from group contexts to bypass authorization checks and perform actions requiring stronger authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2026.3.22, < 2026.6.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenClaw installation versionLocate the OpenClaw application and retrieve its version number (check the application itself, a version file, or the software's about/information page)Affected if The installed version is 2026.3.22 through 2026.6.5 inclusive
-
Confirm WhatsApp integration is activeCheck whether the WhatsApp messaging module or integration is enabled in the OpenClaw configurationAffected if WhatsApp integration is enabled and the version falls within the affected range
-
Locate elevated sender allowlistsFind the authorization configuration that defines elevated-permission sender allowlists within OpenClaw (typically in security, authentication, or permission settings)Affected if Elevated sender allowlists exist and are in use for WhatsApp message handling
-
Verify group messaging authorization logicExamine how the system validates WhatsApp message senders against allowlists, specifically looking for logic that determines whether a message originates from a group versus an individual userAffected if The validation does not properly distinguish between group-sent messages and individual user messages when checking allowlist permissions
-
Review recent authorization logs for group-context actionsSearch authentication or audit logs for actions performed from WhatsApp group contexts that may have bypassed elevated permission checksAffected if Actions were taken using elevated permissions from group-originated messages
The environment is affected if OpenClaw version 2026.3.22 through 2026.6.5 is running with WhatsApp integration enabled and elevated sender allowlists are in use without proper group-versus-individual sender validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.6.6
Upgrade to OpenClaw version 2026.6.6 or later. Additionally, implement proper validation to distinguish WhatsApp group IDs from individual sender IDs in allowlist enforcement, ensuring group contexts cannot satisfy elevated permission requirements.
Upgrade to OpenClaw version 2026.6.6 or later
- Identify the current OpenClaw version in use by checking the application's version endpoint or configuration
- Confirm the installed version falls within the vulnerable range: >= 2026.3.22 and < 2026.6.6
- Plan an upgrade to version 2026.6.6 or later, ensuring to review release notes for any changes
- Before upgrading, perform a full backup of the OpenClaw configuration and data directory
- Schedule a maintenance window to minimize service disruption
- Execute the upgrade process following standard deployment procedures for your environment
- After upgrade, verify the application starts successfully and all services are operational
- Test the WhatsApp sender allowlist functionality to confirm the authorization bypass is remediated - verify that group IDs no longer satisfy elevated sender allowlist requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-62196 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data