openclaw

Ecosystem: npm

Downloads: 11.65 Mln

Vulnerabilities from the last (months)
  • 26CriticalAffects 26 versions
  • 263HighAffects 263 versions
  • 0MediumAffects 0 versions
  • 392ModerateAffects 392 versions
  • 75LowAffects 75 versions
Severity distribution (all time)
756vulnerabilities
  • Critical26 (3.4%)
  • High263 (34.8%)
  • Medium0 (0.0%)
  • Moderate392 (51.9%)
  • Low75 (9.9%)

Monthly breakdown

  • Critical
  • High
  • Medium
  • Moderate
  • Low
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 1
    • Low: 0
  • 41 vulnerabilities
    • Critical: 1
    • High: 23
    • Medium: 0
    • Moderate: 16
    • Low: 1
  • 59 vulnerabilities
    • Critical: 0
    • High: 27
    • Medium: 0
    • Moderate: 21
    • Low: 11
  • 36 vulnerabilities
    • Critical: 2
    • High: 8
    • Medium: 0
    • Moderate: 23
    • Low: 3
  • 209 vulnerabilities
    • Critical: 5
    • High: 47
    • Medium: 0
    • Moderate: 125
    • Low: 32
  • 332 vulnerabilities
    • Critical: 14
    • High: 117
    • Medium: 0
    • Moderate: 178
    • Low: 23
  • 78 vulnerabilities
    • Critical: 4
    • High: 41
    • Medium: 0
    • Moderate: 28
    • Low: 5

Vulnerabilities (756)

Known vulnerabilities affecting openclaw, based on data from OSV.

Vulnerabilities affecting openclaw
IDSeveritySummaryAffected versionsPublishedSource
GHSA-3x84-qq85-fj65ModerateOpenClaw: Browser CDP discovery could accept blocked WebSocket URLs### Summary Browser CDP discovery could accept blocked WebSocket URLs. In affected versions, a lower-trust caller or configured input path could reach network destinations that should have been blocked by OpenClaw policy. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable,
  • < 2026.6.6
GitHub (opens in a new tab)
GHSA-jw7v-5mp7-ghgmModerateDuplicate Advisory: Browser CDP discovery could accept blocked WebSocket URLs## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-3x84-qq85-fj65. This link is maintained to preserve external references. ## Original Description OpenClaw before 2026.6.6 contains a policy bypass vulnerability in browser CDP discovery that accepts blocked WebSocket URLs. Attackers with lower-trust access can reach network destinations that should have been blocked by OpenClaw policy when the affected feature is enabled.
  • < 2026.6.6
GitHub (opens in a new tab)
GHSA-275c-xpvc-jgfwModerateOpenClaw: Slack and Zalo webhook secrets could remain active after secrets.reload### Summary Slack and Zalo webhook secrets could remain active after secrets.reload. In affected versions, a caller with an old webhook secret during the stale-secret window could keep accepting the previous secret after `secrets.reload`. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enable
  • < 2026.4.22
GitHub (opens in a new tab)
GHSA-2hfg-4fh4-qp7fModerateOpenClaw's browser act interactions could bypass private-network navigation checks### Summary OpenClaw's browser control SSRF checks blocked direct navigation to private or loopback URLs, but some Playwright `act` interactions could trigger navigation after the initial check. A later browser evaluation could then read from the page reached by that action-triggered navigation. This issue is specific to browser control actions and private-network navigation policy. Browser evaluation remains an intentional trusted-operator feature when it is used on pages that policy allowed the browser to visit. ### Affected configurations This affects deployments where browser control i
  • < 2026.5.18
GitHub (opens in a new tab)
GHSA-3c6j-hq33-3jv4HighOpenClaw: Paired nodes could forge exec lifecycle events without system.run provenance### Summary OpenClaw nodes send lifecycle events back to the gateway. In affected releases, a paired node could send an exec lifecycle event that was accepted without enough provenance tying it to an authorized `system.run` request. This issue affects the node event boundary. It does not allow an unauthenticated caller to reach the gateway; the attacker must already control a paired node connection. ### Affected configurations This affects deployments with a paired node where that node can send crafted `node.event` messages to the gateway and the target agent/session can process exec lifec
  • < 2026.5.18
GitHub (opens in a new tab)
GHSA-3wqp-prf6-2m72LowOpenClaw: Feishu dynamic-agent bindings could miss configWrites enforcement### Summary Feishu dynamic-agent bindings could miss configWrites enforcement. In affected versions, a Feishu sender using dynamic-agent binding behavior could create or update bindings without honoring the configured config-write control. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabl
  • < 2026.5.6
GitHub (opens in a new tab)
GHSA-4m3v-q747-pc6hModerateOpenClaw: Mattermost slash token revocation could lag until monitor refresh### Summary Mattermost slash token revocation could lag until monitor refresh. In affected versions, a caller with an old Mattermost slash token during the refresh window could continue accepting the old token until the monitor refreshed. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enable
  • < 2026.4.24
GitHub (opens in a new tab)
GHSA-6c4r-g249-wv3cModerateOpenClaw: Sandboxed session spawn could expose the real workspace path to child prompts### Summary Sandboxed session spawn could expose the real workspace path to child prompts. In affected versions, a child session spawned from a sandboxed parent could forward the host workspace path into the child session prompt. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and rea
  • < 2026.4.26
GitHub (opens in a new tab)
GHSA-6fvr-66p3-3qj4HighOpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority### Summary OpenClaw hook ingress can start automated agent runs using a configured hook token. In affected releases, a hook-triggered run could select a bundled CLI backend that received owner-scoped MCP loopback authority instead of a scope appropriate for hook ingress. This issue affects the boundary between hook-token automation and owner-only MCP tools. It does not affect deployments with hooks disabled. ### Affected configurations This affects deployments where hooks are enabled, `/hooks/agent` is reachable with a valid hook token, and a bundled CLI backend can be selected for the ho
  • < 2026.5.20
GitHub (opens in a new tab)
GHSA-77pv-3w4q-vrj5HighOpenClaw: QQBot pre-dispatch slash commands could skip allowFrom checks### Summary QQBot pre-dispatch slash commands could skip allowFrom checks. In affected versions, a QQBot sender able to invoke slash commands could dispatch the command before applying the configured allowFrom policy. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable, this
  • < 2026.4.27
GitHub (opens in a new tab)
  • GHSA-3x84-qq85-fj65Moderate
    OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs
    • < 2026.6.6

    ### Summary Browser CDP discovery could accept blocked WebSocket URLs. In affected versions, a lower-trust caller or configured input path could reach network destinations that should have been blocked by OpenClaw policy. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable,

    CVE: CVE-2026-62197

  • GHSA-jw7v-5mp7-ghgmModerate
    Duplicate Advisory: Browser CDP discovery could accept blocked WebSocket URLs
    • < 2026.6.6

    ## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-3x84-qq85-fj65. This link is maintained to preserve external references. ## Original Description OpenClaw before 2026.6.6 contains a policy bypass vulnerability in browser CDP discovery that accepts blocked WebSocket URLs. Attackers with lower-trust access can reach network destinations that should have been blocked by OpenClaw policy when the affected feature is enabled.

  • GHSA-275c-xpvc-jgfwModerate
    OpenClaw: Slack and Zalo webhook secrets could remain active after secrets.reload
    • < 2026.4.22

    ### Summary Slack and Zalo webhook secrets could remain active after secrets.reload. In affected versions, a caller with an old webhook secret during the stale-secret window could keep accepting the previous secret after `secrets.reload`. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enable

    CVE: CVE-2026-53830

  • GHSA-2hfg-4fh4-qp7fModerate
    OpenClaw's browser act interactions could bypass private-network navigation checks
    • < 2026.5.18

    ### Summary OpenClaw's browser control SSRF checks blocked direct navigation to private or loopback URLs, but some Playwright `act` interactions could trigger navigation after the initial check. A later browser evaluation could then read from the page reached by that action-triggered navigation. This issue is specific to browser control actions and private-network navigation policy. Browser evaluation remains an intentional trusted-operator feature when it is used on pages that policy allowed the browser to visit. ### Affected configurations This affects deployments where browser control i

    CVE: CVE-2026-53812

  • GHSA-3c6j-hq33-3jv4High
    OpenClaw: Paired nodes could forge exec lifecycle events without system.run provenance
    • < 2026.5.18

    ### Summary OpenClaw nodes send lifecycle events back to the gateway. In affected releases, a paired node could send an exec lifecycle event that was accepted without enough provenance tying it to an authorized `system.run` request. This issue affects the node event boundary. It does not allow an unauthenticated caller to reach the gateway; the attacker must already control a paired node connection. ### Affected configurations This affects deployments with a paired node where that node can send crafted `node.event` messages to the gateway and the target agent/session can process exec lifec

    CVE: CVE-2026-53816

  • GHSA-3wqp-prf6-2m72Low
    OpenClaw: Feishu dynamic-agent bindings could miss configWrites enforcement
    • < 2026.5.6

    ### Summary Feishu dynamic-agent bindings could miss configWrites enforcement. In affected versions, a Feishu sender using dynamic-agent binding behavior could create or update bindings without honoring the configured config-write control. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabl

    CVE: CVE-2026-53835

  • GHSA-4m3v-q747-pc6hModerate
    OpenClaw: Mattermost slash token revocation could lag until monitor refresh
    • < 2026.4.24

    ### Summary Mattermost slash token revocation could lag until monitor refresh. In affected versions, a caller with an old Mattermost slash token during the refresh window could continue accepting the old token until the monitor refreshed. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enable

    CVE: CVE-2026-53824

  • GHSA-6c4r-g249-wv3cModerate
    OpenClaw: Sandboxed session spawn could expose the real workspace path to child prompts
    • < 2026.4.26

    ### Summary Sandboxed session spawn could expose the real workspace path to child prompts. In affected versions, a child session spawned from a sandboxed parent could forward the host workspace path into the child session prompt. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and rea

    CVE: CVE-2026-53826

  • GHSA-6fvr-66p3-3qj4High
    OpenClaw: Hook-triggered CLI runs could receive owner MCP tool authority
    • < 2026.5.20

    ### Summary OpenClaw hook ingress can start automated agent runs using a configured hook token. In affected releases, a hook-triggered run could select a bundled CLI backend that received owner-scoped MCP loopback authority instead of a scope appropriate for hook ingress. This issue affects the boundary between hook-token automation and owner-only MCP tools. It does not affect deployments with hooks disabled. ### Affected configurations This affects deployments where hooks are enabled, `/hooks/agent` is reachable with a valid hook token, and a bundled CLI backend can be selected for the ho

    CVE: CVE-2026-53814

  • GHSA-77pv-3w4q-vrj5High
    OpenClaw: QQBot pre-dispatch slash commands could skip allowFrom checks
    • < 2026.4.27

    ### Summary QQBot pre-dispatch slash commands could skip allowFrom checks. In affected versions, a QQBot sender able to invoke slash commands could dispatch the command before applying the configured allowFrom policy. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable, this

    CVE: CVE-2026-53834

Showing 1-10 of 756 vulnerabilities