High

OpenClaw agentic consent bypass via config.patch

IdentifiersCVE-2026-41349CWE-862· Missing Authorization

CVE-2026-41349 is a high-severity authorization flaw in OpenClaw affecting versions prior to 2026.3.28. The vulnerability allows execution approval for LLM agents to be silently disabled through the config.patch parameter. As described in the available disclosure, a remote attacker with low privileges can abuse this behavior to bypass the product's intended consent and execution-approval security control, enabling agent actions to proceed without the expected user authorization. The issue is classified as CWE-862 (missing authorization).

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to bypass OpenClaw's execution approval mechanism and perform unauthorized operations without user consent. Based on the published severity vectors, the impact is high across confidentiality, integrity, and availability, implying that unauthorized agent actions may expose sensitive data, alter system or application state, and disrupt normal operations depending on the permissions and capabilities available to the affected agent or deployment.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, restrict who can modify configuration inputs, especially config.patch, and limit low-privilege remote access to OpenClaw instances. Apply strict authorization checks around configuration changes and execution-approval settings, monitor for unexpected modifications to config.patch or approval-related configuration, and disable or isolate exposed functionality that permits remote configuration manipulation where operationally feasible.

Remediation

Patch, then assume compromise.

Upgrade OpenClaw to version 2026.3.28 or later, as versions before 2026.3.28 are reported vulnerable. Review the vendor's fix referenced by the associated OpenClaw GitHub commit and security advisory, and ensure the execution approval mechanism can no longer be disabled through config.patch by untrusted or insufficiently authorized actors.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

OpenclawOpenclawapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

7 SOURCESView more in app

cvefeed high severityNews

Apr 23, 2026

CVE-2026-41349 - OpenClaw < 2026.3.28 - Agentic Consent Bypass via config.patch

An agentic consent bypass vulnerability in OpenClaw before version 2026.3.28 that allows LLM agents to disable execution approval via the config.patch parameter, enabling unauthorized operations without user consent.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5