ASR AI Security Radar

Back to incidents

AI security incident: OpenClaw: Docker container escape via unvalidated bind mount config injection (GHSA-w...

Incident date: February 18, 2026 | Published: February 25, 2026 | Source: GitHub Security Advisory | Classification confidence: 64%

This incident is part of the public archive. AI-specific signals are limited in the current source material, so source citations should be reviewed closely during triage. Review methodology.

Summary A configuration injection issue in the Docker tool sandbox could allow dangerous Docker options (bind mounts, host networking, unconfined profiles) to be applied, enabling container escape or host data access. ## Affected Packages / Versions - Package: openclaw (npm) - Affected versions: = 2026.2.15 (next release) ## Impact If an attacker can influence sandbox Docker configuration (or an operator pastes untrusted config), they may be able to: - mount sensitive host paths (e.g.

Why This Is AI-Related

This advisory is part of the public incident archive, but the current source material uses limited explicit AI terminology, so the cited sources should be reviewed carefully when judging AI relevance and exposure.

  • Explicit AI-specific signals are limited in the current source material, so use the cited advisory to validate scope during triage.

Affected Workflow

Review the AI product, dependency, and integration points mentioned in the source advisory before broadening remediation.

Likely Attack Path

The advisory indicates a security path that can affect AI applications, assistants, models, or connected automation workflows if the component is deployed.

Impact

The flaw can expose internal data, local files, or connected systems through AI workflow connectors and supporting services. Severity HIGH. Classification confidence 64%. Source channel GHSA.

Detection And Triage Signals

  • New security events tied to the affected component or advisory identifier
  • Changes in AI workflow behavior, access logs, or plugin execution after the advisory window
  • Evidence that the vulnerable version is active in environments that process sensitive data

Recommended Response

  • Confirm whether the affected component can reach internal metadata, local files, or connected data stores.
  • Restrict outbound requests and sensitive data access paths until a patch or mitigation is in place.
  • Inspect logs for unusual downloads, webhook calls, retrieval requests, or responses containing internal content.

Compliance And Business Impact

Even when exploit details are still emerging, delayed triage can widen operational and compliance exposure around AI systems.

Sources

Want alerts like this in real time?

Get notified with incident context, likely impact, and response guidance.

Get Notified

More incidents