OpenclawApplication

CVE-2026-30741

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to after 2026.2.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
A remote code execution (RCE) vulnerability in OpenClaw Agent Platform v2026.2.6 allows attackers to execute arbitrary code via a Request-Side prompt injection attack.

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 confidence

A request-side prompt injection vulnerability in OpenClaw Agent Platform v2026.2.6 allows remote attackers to inject malicious prompts that bypass input controls and execute arbitrary code on the underlying system with the privileges of the agent service.

MitigationImplement strict input validation and sanitization for all prompts entering the agent system, apply least-privilege principles to the agent execution environment, and network-segment the agent platform to limit blast radius if compromised.

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.2.6

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify if OpenClaw Agent Platform is installed
    Look for the OpenClaw service or daemon running on the system, or check for OpenClaw installation directories and binaries.
    Affected if OpenClaw Agent Platform is installed and running on the system.
  2. Determine the installed OpenClaw version
    Run the OpenClaw version command or check the software metadata/package information to obtain the exact version number.
    Affected if The installed version is 2026.2.6 or any earlier version (anything <= 2026.2.6).
  3. Verify the prompt input processing endpoint is enabled
    Check the OpenClaw configuration files or service settings to confirm that the prompt/request processing functionality is active and accessible.
    Affected if The prompt input processing endpoint or module is enabled and accepting external prompts.
  4. Inspect input validation configuration
    Examine the OpenClaw configuration files for settings related to prompt input validation, sanitization, or input filtering controls.
    Affected if Input validation is disabled, set to permissive mode, or missing entirely for prompt processing.

A user is affected if OpenClaw Agent Platform version 2026.2.6 or lower is installed with the prompt input processing feature enabled and without strict input validation controls in place.

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.

From vendor data
Upgrade available Upgrade to a release after 2026.2.6
Interim mitigation

Implement strict input validation and sanitization for all prompts entering the agent system, apply least-privilege principles to the agent execution environment, and network-segment the agent platform to limit blast radius if compromised.

Fix this in Openclaw Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30741 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