GHSA-v8qf-fr4g-28p2 — LOW AI Security Vulnerability

Q: What is GHSA-v8qf-fr4g-28p2?

OpenClaw: Assistant media route missed scope enforcement for trusted-proxy authorization

Q: Is GHSA-v8qf-fr4g-28p2 actively exploited?

No confirmed active exploitation of GHSA-v8qf-fr4g-28p2 has been reported, but organizations should still patch proactively.

Q: How to fix GHSA-v8qf-fr4g-28p2?

Update to patched version: openclaw 2026.4.20.

Q: What is the CVSS score for GHSA-v8qf-fr4g-28p2?

No CVSS score has been assigned yet.

## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `< 2026.4.20` - Patched version: `2026.4.20` ## Impact The Control UI assistant-media route authenticated trusted-proxy callers but did not enforce the declared operator scopes for identity-bearing HTTP auth paths....

Full CISO analysis pending enrichment.

Affected Systems

Package	Ecosystem	Vulnerable Range	Patched
openclaw	npm	< 2026.4.20	`2026.4.20`
2 dependents 93% patched ~1d to patch Full package profile →

Do you use openclaw? You're affected.

Severity & Risk

CVSS 3.1

N/A

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

N/A

Recommended Action

Patch available

Update openclaw to version 2026.4.20

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is GHSA-v8qf-fr4g-28p2?

OpenClaw: Assistant media route missed scope enforcement for trusted-proxy authorization

Is GHSA-v8qf-fr4g-28p2 actively exploited?

No confirmed active exploitation of GHSA-v8qf-fr4g-28p2 has been reported, but organizations should still patch proactively.

How to fix GHSA-v8qf-fr4g-28p2?

Update to patched version: openclaw 2026.4.20.

What is the CVSS score for GHSA-v8qf-fr4g-28p2?

No CVSS score has been assigned yet.

Technical Details

NVD Description

## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `< 2026.4.20` - Patched version: `2026.4.20` ## Impact The Control UI assistant-media route authenticated trusted-proxy callers but did not enforce the declared operator scopes for identity-bearing HTTP auth paths. A trusted-proxy caller without `operator.read` could access assistant-media files and metadata that were otherwise inside allowed media roots. The route still required successful gateway authentication and media-root checks. Severity is low. ## Fix Assistant-media file and metadata requests now require `operator.read` on identity-bearing HTTP auth paths. Fix commit: - `99ef3a63c58440d53f8e45ad861b846032fcb036` ## Release Fixed in OpenClaw `2026.4.20`.