CVE-2026-62187

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 13, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Jul 13, 2026
Patch available. Sources: github.
Web pageMentions a patch (unverified)

OpenClaw < 2026.6.9 Feishu tools Authorization Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-feishu-tools-authorization-bypass
GitHub advisoryMentions a patch (unverified)

Feishu tools could ignore per-account disablement · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-2q7j-2vhx-56g8

Vendor Advisories for CVE-2026-62187(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@openclaw/feishu—
  • every version up to 2026.6.9: fixed in 2026.6.9
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 233 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 133 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-13 13:07 UTCEG score recompute
  3. 2026-10-13 13:07 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-12 15:50 UTCEG score recompute
  6. 2026-10-11 19:34 UTCEG score recompute
  7. 2026-10-11 16:49 UTCEG score recompute
  8. 2026-10-11 14:11 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-08 16:39 UTCEG score recompute
  14. 2026-10-08 16:39 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-10-08 15:45 UTCEG score recompute
  16. 2026-10-08 15:45 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-01 14:11 UTCEG score recompute
  25. 2026-10-01 14:11 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-09-28 09:28 UTCEG score recompute
  4. 2026-09-28 09:28 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-09-24 10:04 UTCEG score recompute
  7. 2026-09-24 10:04 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-09-23 04:17 UTCEG score recompute
  10. 2026-09-23 04:17 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-09-18 05:00 UTCEG score recompute
  14. 2026-09-18 05:00 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-09-14 11:07 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-09-13 23:31 UTCEG score recompute
  19. 2026-09-13 23:31 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-13 07:58 UTCEG score recompute
  21. 2026-09-13 07:58 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-09-12 13:26 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-09-12 01:50 UTCEG score recompute
  24. 2026-09-12 01:50 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-08 01:54 UTCEG score recompute
  29. 2026-09-08 01:54 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-09-06 13:49 UTCEG score recompute
  32. 2026-09-06 13:49 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-05 21:23 UTCEG score recompute
  35. 2026-09-05 21:23 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  36. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-08-31 06:01 UTCEG score recompute
  41. 2026-08-31 06:01 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-08-30 16:53 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  44. 2026-08-30 05:28 UTCEG score recompute
  45. 2026-08-30 05:28 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  48. 2026-08-28 02:32 UTCEG score recompute
  49. 2026-08-28 02:31 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-08-27 13:58 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  52. 2026-08-27 01:13 UTCEG score recompute
  53. 2026-08-27 01:13 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-08-26 13:48 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  56. 2026-08-26 02:20 UTCEG score recompute
  57. 2026-08-26 02:20 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  59. 2026-08-25 09:18 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  60. 2026-08-24 20:43 UTCEG score recompute
  61. 2026-08-24 20:43 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  62. 2026-08-24 09:17 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-08-23 21:02 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-08-23 09:36 UTCEG score recompute
  65. 2026-08-23 09:36 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  67. 2026-08-22 22:09 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  68. 2026-08-22 10:44 UTCEG score recompute
  69. 2026-08-22 10:44 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  70. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  71. 2026-08-21 23:19 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  72. 2026-08-21 11:48 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-08-20 23:59 UTCEG score recompute
  74. 2026-08-20 23:59 UTCGHSA enrichmentGHSA-mm88-h44m-w2gp · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 11th percentile

Related CVEs(same product + same CWE)

Same product

2 shown

npm:@openclaw/feishu

Frequently asked(5)

What is CVE-2026-62187?
CVE-2026-62187 is a high-severity vulnerability; its CVE record was published on July 13, 2026. 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…
When was CVE-2026-62187 made public?
CVE-2026-62187 was made public on June 30, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 13, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-62187 actively exploited?
CVE-2026-62187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62187?
CVE-2026-62187 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62187?
A fix for CVE-2026-62187 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62187 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62187

Explore →

Is Your Infrastructure Affected by CVE-2026-62187?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs