Is this vulnerability remotely exploitable?

Yes. In typical deployments, any remote user who can send messages or replies processed by the QQBot can attempt to exploit the vulnerability by embedding crafted media tags in their content.

What level of access does an attacker need to exploit this?

The attacker needs the ability to interact with the QQBot on the relevant platform (for example, sending messages in a group or channel where the bot is active). No direct filesystem or server access is required; the bot itself becomes the read primitive.

What is the safest general fix pattern for this issue?

The most robust fix is to decouple media tags from raw filesystem paths. Treat tags as opaque identifiers, resolve them through a trusted mapping or database, and ensure any underlying file access is constrained to a well-defined media root directory with canonicalization and boundary checks.

Severity:

HIGH RISK

(8.6)

Path Traversal Arbitrary File Read (CWE-23) in OpenClaw QQBot Media Tags

CVE-2026-43533

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:

Path Traversal / Directory Traversal

CWE:

CWE-23

Impact:

Arbitrary Local File Read / Sensitive Data Exposure

Severity:

HIGH RISK

(8.6)

CVSS Version:

3.1

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-23

Impact:

Arbitrary Local File Read / Sensitive Data Exposure

Severity:

HIGH RISK

(8.6)

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

Path Traversal Arbitrary File Read (CWE-23) in OpenClaw QQBot Media Tags

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