CVE-2026-62199
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 versions before 2026.6.6 contain a flaw in host exec environment filtering that can miss interpreter startup variables. When the affected feature is enabled and reachable, a lower-trust caller or configured input path can supply crafted environment variables to execute or persist actions beyond the caller's intended authorization.
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 versions before 2026.6.6 contain a flaw in host exec environment filtering that fails to properly sanitize interpreter startup variables. When the affected host execution feature is enabled and reachable, a lower-privilege caller or attacker-controllable input path can supply crafted environment variables to bypass authorization and achieve code execution or persistence beyond intended boundaries.
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.6.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify OpenClaw versionLocate the OpenClaw installation and check the version. This may be in the binary itself, a version file, or via a command like 'openclaw --version'. Compare the installed version against 2026.6.6.Affected if Installed version is before 2026.6.6
-
Check if host exec feature is enabledExamine the OpenClaw configuration file for the host exec feature. Look for settings that enable or control the host exec functionality. The exact config file name and location depends on your OpenClaw installation.Affected if Host exec feature is enabled in the configuration
-
Verify environment variable filtering for host execTest the host exec functionality with a controlled execution that includes interpreter startup variables like LD_PRELOAD or LD_LIBRARY_PATH. Inspect whether these variables are passed through to the executed process or properly filtered.Affected if Environment variables such as LD_PRELOAD, LD_LIBRARY_PATH, or PATH equivalents are not filtered and reach the executed process
Environment is affected if OpenClaw version is before 2026.6.6 AND the host exec feature is enabled, allowing unfiltered environment variables to be injected during execution.
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.6.6
Update OpenClaw to version 2026.6.6 or later which includes proper environment variable filtering for host execution. If immediate update is not feasible, disable the host exec feature or restrict input paths to prevent untrusted environment variable injection.
2026.6.6
- Identify all OpenClaw deployments in your environment running versions before 2026.6.6
- Review any use of the host exec feature and environment variable handling configurations
- Upgrade OpenClaw to version 2026.6.6 or later
- After upgrading, verify that the host exec environment filtering now properly handles interpreter startup variables
- Test the affected feature with crafted environment variables to confirm the vulnerability is remediated
- Audit any integration points or lower-trust callers that supply environment variables to ensure they can no longer bypass authorization boundaries
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62199 — 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-62199 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