Skip to content
Applications

CVE-2026-62187

8.6
High
EPSS 0.37%Patch availableJul 14, 2026

Auth bypass in @openclaw/feishu allowing lower-trust callers to perform restricted actions.

common questions

Is CVE-2026-62187 being exploited?

Not confirmed. CVE-2026-62187 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-62187?

CVE-2026-62187 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62187?

Yes. A fix has been recorded for CVE-2026-62187. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62187 affect?

CVE-2026-62187 affects @openclaw/feishu <=2026.6.6, Node.js apps using the package, Services integrating Feishu via this package. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62187?

Upgrade to @openclaw/feishu v2026.6.9 immediately; restrict untrusted inputs if delay is necessary.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
@openclaw/feishu <=2026.6.6Node.js apps using the packageServices integrating Feishu via this package
impact

Authorization bypass lets lower-trust callers or crafted input perform unauthorized Feishu operations, enabling data access or command execution within affected integrations.

action required

Immediate action required

affected versions
openclaw feishu
  • affected< 2026.6.9
vendor says fixed in2026.6.9

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free