Cyber Resilience

CVE-2026-43526

SSRF in Openclaw ≤ 2026.4.12

Public PoCSSRF
Published
05 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v4 8.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0025 17th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2026-43526 is a high-severity SSRF (CWE-918) vulnerability in Openclaw Openclaw. Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-43526 is a server-side request forgery (SSRF) vulnerability, classified as CWE-918, affecting OpenClaw versions prior to 2026.4.12. The flaw exists in the QQBot reply media URL handling component, where the server processes attacker-controlled media URLs by fetching arbitrary content and then re-uploading the retrieved bytes through the channel.

Unauthenticated remote attackers can exploit this vulnerability over the network with low attack complexity and no user interaction required, as indicated by its CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N). By supplying malicious media URLs, attackers trigger SSRF requests to internal or external resources, enabling them to read sensitive data with high confidentiality impact and potentially alter channel content with low integrity impact through the re-upload mechanism.

Mitigation involves upgrading to OpenClaw version 2026.4.12 or later, which incorporates fixes from GitHub commits 08ae021d1f4f02e0ca5fd8a3b9659291c1ecf95a and ddb7a8dd80b8d5dd04aafa44ce7a4354b568bb2d. Further details on the vulnerability and remediation are available in the GitHub Security Advisory at GHSA-2767-2q9v-9326 and the VulnCheck advisory at https://www.vulncheck.com/advisories/openclaw-server-side-request-forgery-via-qqbot-reply-media-url-handling.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

OpenClaw before 2026.4.12 contains a server-side request forgery vulnerability in QQBot reply media URL handling that allows attackers to fetch arbitrary content. Attackers can exploit this by providing malicious media URLs that trigger SSRF requests, with fetched bytes subsequently re-uploaded…

more

through the channel.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22181Same product: Openclaw Openclaw
CVE-2026-44116Same product: Openclaw Openclaw
CVE-2026-28467Same product: Openclaw Openclaw
CVE-2026-32037Same product: Openclaw Openclaw
CVE-2026-53827Same product: Openclaw Openclaw
CVE-2026-41914Same product: Openclaw Openclaw
CVE-2026-41302Same product: Openclaw Openclaw
CVE-2026-44117Same product: Openclaw Openclaw
CVE-2026-62216Same product: Openclaw Openclaw
CVE-2026-62227Same product: Openclaw Openclaw

Affected Assets

openclaw
openclaw
≤ 2026.4.12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References