CVE-2026-62188
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 @openclaw/feishu versions 2026.6.6 and earlier contain an incorrect authorization vulnerability in which the Feishu permission tools could ignore per-account disablement settings. When the affected feature is enabled and reachable, a lower-trust caller or configured input path could perform actions that should have required a stronger authorization or policy check. The issue is fixed in version 2026.6.9.
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's Feishu integration contains an authorization bypass where the permission tools ignore per-account disablement settings, allowing lower-trust callers to perform actions that should require stronger authorization checks.
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.6.9CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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.
-
Check installed @openclaw/feishu package versionRun 'npm list @openclaw/feishu' or check your package-lock.json for the installed version of @openclaw/feishuAffected if The installed version is earlier than 2026.6.9 (e.g., 2026.6.8, 2026.6.0, etc.)
-
Verify Feishu integration is in useCheck your application configuration files (such as config.json, config.yaml, or environment variables) for any 'feishu' or 'openclaw' integration settings that are enabledAffected if Feishu integration is configured and enabled in your environment
-
Inspect permission tool configurationExamine the permission or authorization configuration files for your OpenClaw deployment, looking for per-account disablement settings related to Feishu actionsAffected if Per-account permission disablement settings exist but may be ignored by the permission tools
-
Review audit logs for unauthorized Feishu actionsCheck application logs for any Feishu-related API calls or actions performed by accounts that should have been restricted based on your permission settingsAffected if Actions were performed by lower-trust accounts that should have been blocked according to your configured authorization rules
You are affected if you are running @openclaw/feishu version earlier than 2026.6.9 AND have the Feishu integration enabled with authorization rules that rely on per-account disablement settings.
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.9
Upgrade @openclaw/feishu to version 2026.6.9 or later to resolve the incorrect authorization vulnerability.
2026.6.9
- Identify all systems running OpenClaw/feishu versions before 2026.6.9
- Review current configuration and note any custom permission settings
- Create a backup of existing configuration and data
- Upgrade OpenClaw/feishu to version 2026.6.9 or later
- After upgrade, verify that the Feishu permission tools correctly enforce per-account disablement settings
- Test that authorization checks are properly applied to actions that should require stronger permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62188 — 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-62188 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