CVE-2026-41363
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.2.6 through 2026.3.24 contain a path traversal vulnerability in the Feishu extension resolveUploadInput function that bypasses file-system sandbox restrictions. Attackers can exploit improper path resolution during upload_image operations to read arbitrary files outside configured localRoots boundaries.
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.2.6-2026.3.24 contain a path traversal vulnerability in the Feishu extension's resolveUploadInput function. The function improperly resolves file paths during upload_image operations, allowing attackers to bypass configured localRoots sandbox restrictions and read arbitrary files from the filesystem.
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.6, < 2026.3.28CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installation and versionRun the version command or check the software manifest to determine the installed OpenClaw version.Affected if The installed version falls within 2026.2.6 to 2026.3.24 inclusive.
-
Confirm Feishu extension is enabledInspect the OpenClaw extension configuration or plugin settings to verify whether the Feishu integration module is active.Affected if The Feishu extension is enabled in the configuration.
-
Verify upload_image feature is accessibleCheck whether the upload_image operation is exposed through the Feishu extension API or web interface.Affected if Users have access to the upload_image functionality in the Feishu extension.
-
Inspect localRoots configurationReview the OpenClaw configuration file or settings to identify the defined localRoots boundaries for file operations.Affected if localRoots are configured (the vulnerability exploits bypassing these boundaries).
A user is affected if OpenClaw version 2026.2.6-2026.3.24 is running with the Feishu extension enabled and upload_image operations are accessible.
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.3.28
Upgrade to a version beyond 2026.3.24 or apply vendor patch. Additionally, implement strict path validation in resolveUploadInput to ensure resolved paths remain within permitted localRoots boundaries before any file access.
OpenClaw 2026.3.28 or later
- 1. Identify the current OpenClaw version installed in your environment
- 2. Backup your current configuration and data directories before upgrading
- 3. Upgrade OpenClaw to version 2026.3.28 or later
- 4. Verify the Feishu extension is updated to the version bundled with the new release
- 5. Test file upload operations to confirm the path traversal fix is working correctly
- 6. Review the changelog for version 2026.3.28 to ensure all security fixes are applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41363 — 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-41363 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