CVE-2026-41390
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 · uneditedOpenClaw before 2026.3.28 contains an exec allowlist bypass vulnerability where allow-always persistence fails to unwrap /usr/bin/script and similar wrappers before storing trust decisions. Attackers can obtain user approval for one wrapped command to persist trust for wrapper binaries that execute different underlying programs.
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 · moderate confidenceOpenClaw's execution allowlist has a bypass vulnerability where the trust persistence mechanism fails to unwrap wrapper binaries like /usr/bin/script before making trust decisions. An attacker can obtain user approval for a wrapped command, which then persists trust for that wrapper binary. Since the wrapper can execute different underlying programs, the attacker can bypass the allowlist by having the trusted wrapper run arbitrary executables.
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< 2026.3.28CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed OpenClaw versionRun 'openclaw --version' or check the package manager for the installed version of OpenClawAffected if The installed version is lower than 2026.3.28
-
Inspect trust persistence storageExamine the configuration file or database where OpenClaw stores trusted execution decisions (commonly in ~/.config/openclaw/ or /etc/openclaw/)Affected if The trust database contains entries for wrapper binaries like /usr/bin/script without records of the underlying programs they were used to execute
-
Review wrapper binary trust entriesSearch the trust configuration for entries that reference /usr/bin/script or similar system wrapper utilitiesAffected if Wrapper binaries are listed as individually trusted without evidence of unwrapping to the actual target executable
-
Verify trust decision logicExamine OpenClaw configuration for settings related to trust persistence and wrapper unwrapping behaviorAffected if There is no configuration or it explicitly stores trust for the wrapper binary rather than resolving and storing trust for the final executable
-
Test allowlist enforcement with wrapperUse a wrapper binary like /usr/bin/script to execute an arbitrary command not on the allowlist and observe if it is permittedAffected if The wrapped command executes successfully despite the underlying executable being on the deny list or not on the allow list
You are affected if OpenClaw version is below 2026.3.28 AND the trust persistence mechanism stores approval for wrapper binaries rather than resolving them to their target executables, allowing any program to be run through a trusted wrapper.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.3.28
Update to OpenClaw version 2026.3.28 or later, which should implement proper unwrapping of wrapper binaries before storing trust decisions to prevent allowlist bypass.
2026.3.28
- Upgrade OpenClaw to version 2026.3.28 or later to resolve the exec allowlist bypass vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41390 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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