CVE-2026-32914
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.12 contains an insufficient access control vulnerability in the /config and /debug command handlers that allows command-authorized non-owners to access owner-only surfaces. Attackers with command authorization can read or modify privileged configuration settings restricted to owners by exploiting missing owner-level permission checks.
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 before 2026.3.12 has an authorization bypass in the /config and /debug command handlers where missing owner-level permission checks allow command-authorized (non-owner) users to access owner-restricted surfaces. Attackers with standard command authorization can read or modify privileged configuration settings that should be limited to owner accounts only.
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.12CVSS 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 installation versionCheck the installed OpenClaw version by examining the application binary, package metadata, or running 'openclaw --version' if CLI is available. Compare against the affected range: versions prior to 2026.3.12 are vulnerable.Affected if Installed version is before 2026.3.12
-
Verify /config endpoint accessibilityAttempt to access the /config HTTP endpoint or command handler using a non-owner account that has command authorization but not owner privileges. Observe whether the request is granted or rejected.Affected if Non-owner users can access /config endpoint without being blocked
-
Verify /debug endpoint accessibilityAttempt to access the /debug HTTP endpoint or command handler using a non-owner account that has command authorization but not owner privileges. Observe whether the request is granted or rejected.Affected if Non-owner users can access /debug endpoint without being blocked
-
Confirm privilege escalation on config settingsAs a non-owner user with command access, attempt to read or modify privileged configuration settings through the /config handler. Verify if sensitive settings intended only for owners are exposed or editable.Affected if Non-owner users can read or modify owner-restricted configuration settings
A user is affected if they run any OpenClaw version prior to 2026.3.12 and have non-owner accounts that can access the /config or /debug handlers without proper owner-level permission enforcement.
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.
From vendor data2026.3.12
Upgrade to OpenClaw version 2026.3.12 or later which implements proper owner-level permission checks. Until patched, limit command authorization to highly trusted users and monitor access to /config and /debug endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32914 — 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-32914 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