CVE-2026-43533: OpenClaw · QQBot media tags could read arbitrary local files through reply text
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 8.9 High : upgrade to 2026.4.10 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.4.10
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 May 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 17 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.4.10.
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
Users should upgrade to openclaw version 2026.4.10 or later to remediate this vulnerability. The fix enforces proper media storage boundaries, preventing local file disclosure through QQBot media tags. The latest npm release, 2026.4.14, includes this fix. No additional mitigation steps are required once upgraded.
Description
A vulnerability in the openclaw CLI's QQBot media tags allows reading arbitrary local files via reply text. This occurs because outbound media tags can reference local file paths outside the intended media storage boundary, leading to local file disclosure. The issue affects openclaw versions before 2026.4.10 and was fixed in version 2026.4.10 and later.