Is this vulnerability remotely exploitable?

Yes. Anyone who can cause the QQBot to process a reply with a crafted media URL can potentially trigger SSRF, subject to how messages are authenticated and routed in a given deployment.

What level of access does an attacker need?

Typically, the attacker needs the ability to send or influence messages that the QQBot will process—such as being a member of a QQ channel the bot participates in or controlling an integration that feeds messages into the bot.

What is the safest general fix pattern?

The safest pattern is to restrict outbound requests to a narrow set of allowed domains through an allowlist, combined with network-level egress controls that prevent access to internal IP ranges and sensitive endpoints, and to validate and normalize URLs before dereferencing them.

Severity:

HIGH RISK

(8.2)

Server-Side Request Forgery (CWE-918) in OpenClaw QQBot Media URL Handling

CVE-2026-43526

Published:

May 5, 2026

Status:

Undergoing Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Unauthorized access to internal and external resources via SSRF, with potential data exfiltration and pivoting

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Unauthorized access to internal and external resources via SSRF, with potential data exfiltration and pivoting

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Server-Side Request Forgery (CWE-918) in OpenClaw QQBot Media URL Handling

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal