CVE-2026-41914: Openclaw cli · OpenClaw QQ Bot Extension missing SSRF Protection on All Media Fetch Paths
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2026.4.8 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in openclaw npm package version 2026.4.8. Users should upgrade to this version or later to remediate the SSRF protection issue. The fix has been verified with regression tests. No additional mitigation actions are indicated by the vendor advisory.
Description
OpenClaw CLI's QQ Bot Extension had missing Server-Side Request Forgery (SSRF) protection on all media fetch paths, allowing user-controlled local assistants to bypass SSRF guard and allowlist policies. This vulnerability affects openclaw npm package versions from 2026.1.29 up to but not including 2026.4.8. The issue was fixed in version 2026.4.8 with targeted regression tests verifying the fix.