CVE-2026-28466
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 prior to 2026.2.14 contain a vulnerability in the gateway in which it fails to sanitize internal approval fields in node.invoke parameters, allowing authenticated clients to bypass exec approval gating for system.run commands. Attackers with valid gateway credentials can inject approval control fields to execute arbitrary commands on connected node hosts, potentially compromising developer workstations and CI runners.
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 confidenceOpenClaw gateway versions before 2026.2.14 fail to sanitize internal approval fields in node.invoke parameters, allowing authenticated gateway users to bypass exec approval gating for system.run commands and execute arbitrary commands on connected node hosts.
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.2.14CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 gateway installationLocate the OpenClaw gateway installation and determine its installed version using the system's package manager, configuration files, or binary version flag (e.g., openclaw-gateway --version or similar)Affected if The gateway is present and reports a version lower than 2026.2.14
-
Verify node.invoke functionality usageInspect gateway logs, audit trails, or configuration to determine whether node.invoke API calls are being made, particularly with system.run command parametersAffected if The gateway has processed node.invoke requests containing system.run commands without proper approval field sanitization being visible in logs or audit records
-
Confirm connected node hosts existReview the gateway's node host registry, connection inventory, or management console to list active node hosts connected to the gatewayAffected if One or more node hosts are registered and connected to the vulnerable gateway version, as these are the targets for arbitrary command execution
-
Check approval gating configurationExamine the gateway's approval workflow settings, particularly the exec approval gating mechanism for system.run commands, to determine if it is enabledAffected if The approval gating is configured but can be bypassed due to the unsanitized internal approval fields in node.invoke parameters
You are affected if OpenClaw gateway version is below 2026.2.14, node.invoke with system.run is in use, and node hosts are connected to the gateway, allowing potential bypass of approval controls.
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.2.14
Upgrade OpenClaw to version 2026.2.14 or later to obtain the patched gateway that properly sanitizes approval control fields.
2026.2.14
- Upgrade OpenClaw gateway to version 2026.2.14 or later
- After upgrading, verify that the gateway properly sanitizes internal approval fields in node.invoke parameters
- Test that the exec approval gating for system.run commands is enforced correctly after the upgrade
- Review audit logs to ensure no unauthorized command execution occurred prior to the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28466 — 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-28466 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