dbcve.org
Openclaw\/feishuApplication · Openclaw

CVE-2026-62187

HIGH · 8.1 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2026.6.9 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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 · unedited
OpenClaw Feishu tools (npm package @openclaw/feishu) in versions <= 2026.6.6 could ignore per-account disablement. A lower-trust caller or a configured input path could perform actions that should have required a stronger authorization or policy check, resulting in unauthorized operations. The issue is fixed in version 2026.6.9. Impact depends on the operator's configuration and whether lower-trust input can reach 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 confidence

The @openclaw/feishu npm package versions 2026.6.6 and earlier contained an authorization bypass where per-account disablement settings were ignored, allowing lower-trust callers or configured input paths to perform actions requiring stronger authorization.

MitigationUpgrade to version 2026.6.9 or later. Review and audit configurations to ensure lower-trust input paths cannot reach affected features until the upgrade is applied.

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
Openclaw\/feishuApplication
Affected:< 2026.6.9

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed package version
    Run 'npm list @openclaw/feishu' or inspect your package.json dependencies to find the installed version of @openclaw/feishu
    Affected if The installed version is 2026.6.6 or earlier (any version before 2026.6.9)
  2. Identify authorization configuration
    Search your project for configuration files (such as config.json, config.js, or environment variables) that contain settings related to account disablement, authorization levels, or trust settings for the feishu integration
    Affected if Per-account disablement or authorization trust settings are configured but the package version is vulnerable
  3. Verify authorization enforcement
    Test or inspect logs to determine whether lower-trust callers or input paths can access features that should be restricted by per-account disablement settings
    Affected if Actions requiring stronger authorization succeed when triggered through lower-trust paths despite disablement settings being configured
  4. Audit configured input paths
    Review your application's input routing or webhook configurations to identify which paths or callers can reach the @openclaw/feishu package functionality
    Affected if Lower-trust input paths or external callers are configured to reach the package's affected features

You are affected if the installed @openclaw/feishu version is 2026.6.6 or earlier AND you use per-account disablement settings or have lower-trust callers that could reach restricted features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.6.9 or later
Fixed in 2026.6.9
Interim mitigation

Upgrade to version 2026.6.9 or later. Review and audit configurations to ensure lower-trust input paths cannot reach affected features until the upgrade is applied.

Recommended fix Moderate confidence

2026.6.9

  1. Check the current version of @openclaw/feishu in your project by running: npm list @openclaw/feishu
  2. Upgrade the package to version 2026.6.9 or later using: npm install @openclaw/feishu@^2026.6.9
  3. Verify the upgrade was successful by running: npm list @openclaw/feishu
  4. Review your application's authorization configuration to ensure lower-trust inputs cannot reach sensitive features, as recommended in the CVE description

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw\/feishu Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62187 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-62187 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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