CVE-2026-41908: OpenClaw < 2026.4.20 - Scope Enforcement Bypass in Assistant-Media Route
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.
Other sources
OpenClaw before 2026.4.20 contains a scope enforcement bypass vulnerability in the assistant-media route that allows trusted-proxy callers without operator.read scope to access protected assistant-media files and metadata. Attackers can bypass identity-bearing HTTP auth path scope validation to retrieve sensitive media content within allowed media roots.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41908?
CVE-2026-41908 is categorized as a high severity vulnerability due to its potential to allow unauthorized access to sensitive assistant-media files.
How do I fix CVE-2026-41908?
To fix CVE-2026-41908, upgrade OpenClaw to version 2026.4.20 or later, which contains a patch for this vulnerability.
What systems are affected by CVE-2026-41908?
CVE-2026-41908 affects OpenClaw versions prior to 2026.4.20.
What kind of attacks can exploit CVE-2026-41908?
Attackers can exploit CVE-2026-41908 to access protected assistant-media files and metadata without the necessary permissions.
Is CVE-2026-41908 easy to exploit?
CVE-2026-41908 can be exploited by trusted-proxy callers, making it relatively easier for those with specific access to misuse.