CVE-2026-62198
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 2026.5.28 before 2026.6.6 contain an authorization bypass vulnerability in native web search that allows lower-trust callers to perform actions requiring stronger policy checks. Attackers can exploit misconfigured input paths to bypass intended authorization controls and execute restricted operations.
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 2026.5.28 through 2026.6.5 have an authorization bypass in the native web search component. The vulnerability stems from misconfigured input path handling that allows lower-privilege callers to bypass policy checks and execute operations requiring higher trust levels.
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.5.28, < 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenClaw installationLocate the OpenClaw installation directory or check running processes for 'openclaw' executable or serviceAffected if OpenClaw is not installed - not affected
-
Determine installed OpenClaw versionRun 'openclaw --version' or check version file in installation directory (e.g., version.txt, about dialog)Affected if Version is 2026.5.28 through 2026.6.5 (inclusive) - potentially affected
-
Verify web search component is enabledCheck configuration files (openclaw.conf, settings.xml) for 'websearch', 'search', or 'web' module entries set to enabled=trueAffected if Web search component is disabled - not vulnerable as feature is not in use
-
Inspect web search authorization configurationExamine authz/policy files in the web search module directory for any allow/deny rules or trust level definitionsAffected if Policy rules exist but contain misconfigured path handling or trust level assignments - may indicate vulnerability is present
User is affected if OpenClaw version is 2026.5.28 through 2026.6.5 AND the web search component is enabled in their configuration.
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
Review and enforce proper authorization validation in the web search module, ensuring all input paths undergo consistent policy enforcement regardless of caller trust level.
OpenClaw 2026.6.6 or later
- 1. Identify all deployed instances running OpenClaw versions between 2026.5.28 and 2026.6.5 (inclusive)
- 2. Review current deployment mechanism (package manager, container registry, or source build)
- 3. Upgrade OpenClaw to version 2026.6.6 or later
- 4. Verify the upgrade completed successfully
- 5. Test that the native web search functionality works correctly post-upgrade
- 6. Confirm authorization controls are enforced properly for lower-trust callers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62198 — 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-62198 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