OpenClaw (formerly Clawdbot) is a personal AI assistant users run on their own devices. In versions 2026.2.2 and below, when the Slack integration is enabled, channel metadata (topic/description) can be incorporated into the model's system prompt. Prompt injection is a documented risk for LLM-driven systems. This issue increases the injection surface by allowing untrusted Slack channel metadata to be treated as higher-trust system input. This issue has been fixed in version 2026.2.3.
CVE-2026-24764
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(low)
- EG Risk
- 21(Track)EG Risk 21/100SSVC: Track
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 computedSeverity37% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/openclaw/openclaw/commit/35eb40a7000b59085e9c638a80fd03917c7a095e
- security-advisories@githubhttps://github.com/openclaw/openclaw/releases/tag/v2026.2.3
- security-advisories@githubhttps://github.com/openclaw/openclaw/security/advisories/GHSA-782p-5fr5-7fj8
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:27 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-94 · CWE-74
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2005-3056EG 9.8CRITICAL
- CVE-2006-1301EG 9.3EPSS p95HIGH
- CVE-2006-1304EG 9.3EPSS p95HIGH
- CVE-2006-1306EG 9.3EPSS p95HIGH
- CVE-2006-1303EG 9.3EPSS p98HIGH
- CVE-2005-3650EG 9.3EPSS p93HIGH
Frequently asked(5)
What is CVE-2026-24764?
When was CVE-2026-24764 disclosed?
Is CVE-2026-24764 actively exploited?
What is the CVSS score of CVE-2026-24764?
How do I remediate CVE-2026-24764?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-24764
Is Your Infrastructure Affected by CVE-2026-24764?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.