Skip to main content
VulnerabilityPublished Updated

CVE-2026-41908: OpenClaw · Assistant media route missed scope enforcement for trusted-proxy authorization

Affects openclawSource GCVE Database

0

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2026.4.20 when convenient.

Data as of 27 Oct 2026, 01:26 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2026.4.20
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade openclaw to 2026.4.20.

Affected software

ProductAffectedFixed in
npmopenclawAffected
  • <2026.4.20
Fixed in
  • 2026.4.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OpenClaw to version 2026.4.20 or later, where the vulnerability is fixed by enforcing the operator.read scope on identity-bearing HTTP auth paths for assistant-media file and metadata requests. No additional mitigation is required as the fix addresses the scope enforcement issue directly.

Description

OpenClaw versions prior to 2026.4.20 contain a vulnerability in the assistant-media route where trusted-proxy callers were authenticated but the enforcement of operator scopes on identity-bearing HTTP auth paths was missing. This allowed trusted-proxy callers without the required operator.read scope to access assistant-media files and metadata within allowed media roots. The route still required gateway authentication and media-root checks. The issue is fixed in version 2026.4.20.

References

Community reviews

Loading reviews…