dbcve.org
OpenclawApplication

CVE-2026-41332

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

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 environment variable sanitization vulnerability where GIT_TEMPLATE_DIR and AWS_CONFIG_FILE are not blocked in the host-env blocklist. Attackers can exploit approved exec requests to redirect git or AWS CLI behavior through attacker-controlled configuration files to execute untrusted code or load malicious credentials.

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 version 2026.3.28 fails to block the GIT_TEMPLATE_DIR and AWS_CONFIG_FILE environment variables in its host-env blocklist. Attackers with the ability to make approved exec requests can set these variables to point to attacker-controlled configuration files, enabling arbitrary code execution via git template hooks or credential theft via malicious AWS config.

MitigationUpdate the host-env blocklist to include GIT_TEMPLATE_DIR and AWS_CONFIG_FILE, and audit the broader blocklist for similar gaps in environment variable coverage.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

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

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. Check OpenClaw version
    Run the OpenClaw version command or inspect the installed package metadata to determine the exact version number
    Affected if The installed version is earlier than 2026.3.28
  2. Locate host-env blocklist configuration
    Find the OpenClaw configuration file that defines the host-env blocklist (commonly a config file or manifest listing blocked environment variables)
    Affected if The blocklist configuration exists and is being applied to exec requests
  3. Inspect blocked environment variables
    Examine the blocklist contents to list all currently blocked environment variables
    Affected if The blocklist is in use and defines environment variable restrictions
  4. Verify GIT_TEMPLATE_DIR is blocked
    Search the blocklist for the presence of GIT_TEMPLATE_DIR
    Affected if GIT_TEMPLATE_DIR is NOT found in the blocklist (absent means vulnerable)
  5. Verify AWS_CONFIG_FILE is blocked
    Search the blocklist for the presence of AWS_CONFIG_FILE
    Affected if AWS_CONFIG_FILE is NOT found in the blocklist (absent means vulnerable)

You are affected if running OpenClaw version before 2026.3.28 AND your host-env blocklist does not include both GIT_TEMPLATE_DIR and AWS_CONFIG_FILE, allowing untrusted exec requests to manipulate these variables for code execution or credential theft.

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

Update the host-env blocklist to include GIT_TEMPLATE_DIR and AWS_CONFIG_FILE, and audit the broader blocklist for similar gaps in environment variable coverage.

Recommended fix High confidence

2026.3.28

  1. Check the current Openclaw version by running the version command or checking the build metadata
  2. Upgrade Openclaw to version 2026.3.28 or later release
  3. Verify the upgrade was successful by confirming the version number
  4. Verify that the environment variables GIT_TEMPLATE_DIR and AWS_CONFIG_FILE are now properly blocked in the host-env blocklist configuration

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41332 — 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-41332 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