Skip to main content
VulnerabilityPublished Updated

CVE-2026-43533: OpenClaw · QQBot media tags could read arbitrary local files through reply text

Affects openclawSource GCVE Database

0
Authoritative record:CVE-2026-43533· High 8.9

Not known to be exploited · CVSS 8.9 High : upgrade to 2026.4.10 soon.

Data as of 27 Oct 2026, 01:37 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade openclaw to 2026.4.10.

Affected software

ProductAffectedFixed in
npmopenclawAffected
  • <2026.4.10
Fixed in
  • 2026.4.10

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 openclaw to version 2026.4.10 or later. The fix is included starting with 2026.4.10, and the latest release 2026.4.14 already contains the patch. No other mitigation actions are indicated.

Description

A vulnerability in the openclaw npm package (versions before 2026.4.10) allows QQBot media tags in AI reply text to read arbitrary local files outside the intended media storage boundary. This local file disclosure issue was fixed in version 2026.4.10 and later.

References

Community reviews

Loading reviews…