PatchSiren cyber security CVE debrief
CVE-2026-62211 OpenClaw CVE debrief
CVE-2026-62211 is a medium-severity vulnerability in OpenClaw versions before 2026.6.1. The vulnerability is caused by a credential redaction bypass in the trajectory export feature, which allows lower-trust callers to access sensitive data that should remain within trusted boundaries. Attackers can exploit misconfigured input paths or feature accessibility to expose sensitive credentials and data through the export mechanism. This vulnerability has a CVSS score of 4.1, indicating a medium severity level. Users of OpenClaw versions before 2026.6.1 should apply the patch to prevent exploitation of this vulnerability.
- Vendor
- OpenClaw
- Product
- Unknown
- CVSS
- MEDIUM 4.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-17
- Original CVE updated
- 2026-07-29
- Advisory published
- 2026-07-17
- Advisory updated
- 2026-07-29
Who should care
Users of OpenClaw versions before 2026.6.1 should apply the patch to prevent exploitation of this vulnerability. This vulnerability is rated as medium severity with a CVSS score of 4.1. Affected operators, platforms, vulnerability-management, and security teams should review and update input paths and feature accessibility to prevent exploitation.
Technical summary
OpenClaw versions before 2026.6.1 contain a credential redaction bypass vulnerability in the trajectory export feature. This vulnerability allows lower-trust callers to access data that should remain within trusted boundaries. The vulnerability can be exploited by attackers who can access misconfigured input paths or feature accessibility to expose sensitive credentials and data through the export mechanism. The Common Vulnerability Scoring System (CVSS) score for this vulnerability is 4.1, indicating a medium severity level.
Defensive priority
Apply the patch for OpenClaw versions before 2026.6.1 to prevent exploitation of this vulnerability. Review and update input paths and feature accessibility to prevent exploitation. Monitor for suspicious activity related to the trajectory export feature.
Recommended defensive actions
- Apply the patch for OpenClaw versions before 2026.6.1
- Review and update input paths and feature accessibility to prevent exploitation
- Monitor for suspicious activity related to the trajectory export feature
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record was published on 2026-07-17T02:18:07.620Z and has not been modified since then. The NVD entry is currently Received. There is limited evidence available to confirm affected scope and severity. Defenders should verify OpenClaw versions before 2026.6.1 for potential exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-62211 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-62211
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-62211 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-62211
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/openclaw/openclaw/security/advisories/GHSA-j4cx-jvq7-79vm
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/openclaw-credential-redaction-bypass-via-trajectory-export
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.