Skip to main content
CVE-2026-100569VulnerabilityPublished

openclaw · In versions >= 2026.4.25 and < 2026.8.1, the workspace environment-variable filter did not block variables ending in

Affects openclawSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 2026.8.1 when convenient.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.8.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 10 Nov 2026.

What to do

Upgrade openclaw/openclaw to 2026.8.1.

Affected software

ProductAffectedFixed in
GitHubopenclaw/openclawpkg:github/openclaw/openclawOther threatsAffected
  • >=2026.4.25 <2026.8.1
Fixed in
  • 2026.8.1

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.8.1 or later, where this vulnerability is fixed. Until then, operators should avoid starting OpenClaw in untrusted or attacker-controlled workspace environments with Azure Speech configured and no trusted endpoint override. No other mitigations are specified.

Description

OpenClaw is an npm-distributed application. In versions >= 2026.4.25 and < 2026.8.1, the workspace environment-variable filter did not block variables ending in `_ENDPOINT`, so an untrusted workspace `.env` file could set AZURE_SPEECH_ENDPOINT. Azure Speech preferred that value over the configured region, so when a synthesis or voice-list request was made, the attacker-selected endpoint received the operator's Azure Speech key in the request header, allowing the key to be reused against the operator's Azure Speech resource. Exploitation requires an operator to start OpenClaw in attacker-controlled workspace content with Azure Speech configured with a key and region and no trusted endpoint override set. The issue is fixed in 2026.8.1.

References

Community reviews

Loading reviews…