dbcve.org
OpenclawApplication

CVE-2026-41380

HIGH · 7.3 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenClaw before 2026.3.28 contains an execution approval vulnerability in exec-approvals-allowlist.ts that allows allow-always persistence to trust wrapper carrier executables instead of invoked targets. Attackers can exploit positional carrier executable routing through dispatch wrappers to establish broader allowlist entries than intended, weakening execution approval boundaries.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenClaw before 2026.3.28 has an execution approval vulnerability in the allowlist mechanism (exec-approvals-allowlist.ts). The system incorrectly trusts 'wrapper carrier executables' (dispatch wrappers that route to multiple targets) rather than the actual invoked target executables. Attackers can exploit this by targeting the wrapper to get broader allowlist coverage than intended, weakening execution approval boundaries.

MitigationUpgrade to OpenClaw 2026.3.28 or later. Additionally, audit and tighten the execution allowlist to ensure only specific target executables are allowlisted, not wrapper/carrier executables that can route to multiple targets.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.3.28

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine OpenClaw installed version
    Run the OpenClaw version command (such as openclaw --version) or check the package manifest, configuration file, or assembly metadata where OpenClaw is installed
    Affected if Version is earlier than 2026.3.28
  2. Locate execution allowlist configuration
    Find the exec-approvals-allowlist.ts file or its compiled/transformed equivalent in the OpenClaw installation directory or configuration repository
    Affected if The allowlist configuration file exists and is actively used by the system
  3. Inspect allowlist entries for wrapper/carrier executables
    Review each entry in the allowlist and identify any executables that function as dispatch wrappers or carriers capable of routing to multiple different target executables, rather than pointing to a single specific executable
    Affected if One or more entries in the allowlist are wrapper or carrier executables that can invoke multiple targets
  4. Assess allowlist scope against intended targets
    Compare the allowlist entries to the actual executables users need to run; check if any single allowlist entry provides coverage beyond one specific target executable
    Affected if Allowlist entries grant broader execution coverage than the specific individual targets they should cover

Environment is affected if OpenClaw version is below 2026.3.28 AND the execution allowlist contains wrapper/carrier executables (dispatch wrappers) rather than only specific target executables.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.3.28 or later
Fixed in 2026.3.28
Interim mitigation

Upgrade to OpenClaw 2026.3.28 or later. Additionally, audit and tighten the execution allowlist to ensure only specific target executables are allowlisted, not wrapper/carrier executables that can route to multiple targets.

Recommended fix Moderate confidence

OpenClaw 2026.3.28 or later

  1. 1. Identify the current OpenClaw installation by checking the version number in use (e.g., via CLI command 'openclaw --version' or inspecting package.json)
  2. 2. Review the current exec-approvals-allowlist.ts configuration file for any suspicious or unexpected allowlist entries that may have been added through the vulnerability
  3. 3. Backup the current configuration and any custom allowlist entries before proceeding
  4. 4. Upgrade OpenClaw to version 2026.3.28 or later using the appropriate package manager (e.g., 'npm install openclaw@latest' or 'pip install openclaw==2026.3.28' depending on the distribution method)
  5. 5. After upgrade, verify the version is correct by running 'openclaw --version'
  6. 6. Audit all execution allowlist entries in the updated exec-approvals-allowlist.ts to ensure only intended entries remain
  7. 7. Test the execution approval system to confirm the fix properly enforces approvals on invoked targets rather than wrapper carriers
Caveat Review custom allowlist configurations after upgrade as the fix may change how entries are interpreted; test execution approval workflows before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41380 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data