OpenClaw before 2026.5.28 contains a race condition in the MS Teams safeFetch DNS rebinding check. When the affected feature is enabled and reachable, a lower-trust caller or configured input path could win a timing window between the DNS validation check and use, allowing actions that should have required a stronger authorization or policy check. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/openclaw/openclaw/security/advisories/GHSA-wxm8-ghhq-q688 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.1 · openclawNVD modified 2026-10-24 13:10
Affected (CPE criteria) 1
cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:*
References 2
- https://github.com/openclaw/openclaw/security/advisories/GHSA-wxm8-ghhq-q688 Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/openclaw-authentication-bypass-via-safefetch Third Party Advisory