Skip to main content
VulnerabilityPublished Updated

CVE-2026-43526: OpenClaw · QQBot reply media URL handling could trigger SSRF and re-upload fetched bytes

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-43526· High 8.3

Not known to be exploited · CVSS 8.3 High : upgrade to 2026.4.12 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.4.12
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/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. Weaponized: 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 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.4.12.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.4.12
Fixed in
  • 2026.4.12

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-cli to version 2026.4.12 or later. The fix is included starting from 2026.4.12, with the latest npm release 2026.4.14 containing the patch. No additional mitigation is required once upgraded.

Description

A vulnerability in openclaw-cli versions before 2026.4.12 allows QQBot reply media URL handling to trigger server-side request forgery (SSRF) and re-upload fetched bytes. This occurs because QQBot media URLs were treated as trusted sources, enabling SSRF fetches whose responses were then re-uploaded. The issue is fixed in version 2026.4.12 and later.

References

Community reviews

Loading reviews…