CVE-2026-32024

OpenClaw avatar handling allowed a symlink traversal path that could expose local files outside an agent workspace through gateway avatar surfaces.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.2.21, plus prereleases 2026.2.21-1 and 2026.2.21-2
• Latest published version at triage time (2026-02-22): 2026.2.21-2 (affected)
• Planned patched version (pre-set for release workflow): 2026.2.22

Details

In vulnerable builds, local avatar resolution could follow symlinks and return file bytes from outside the configured workspace boundary.

The issue was hardened in two paths:

1. Gateway avatar metadata resolution now enforces canonical containment, O_NOFOLLOW, and fd/file-identity checks.
2. Control UI avatar serving now rejects symlink paths and enforces fd/file-identity and size checks before reads.

Fix Commit(s)

• 3d0337504349954237d09e4d957df5cb844d5e77
• 6970c2c2db3ee069ef0fff0ade5cfbdd0134f9d2

Release Process Note

patched_versions is pre-set to >= 2026.2.22 so after npm release, the remaining action is to publish this advisory.

Confidentiality impact only: local files readable by the OpenClaw process could be disclosed via avatar response surfaces.

OpenClaw thanks @tdjackey for reporting.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-32024 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.22); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-32024? CVE-2026-32024 is a medium-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-32024? CVE-2026-32024 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32024? openclaw (npm) versions < 2026.2.22 is affected.
4. Is there a fix for CVE-2026-32024? Yes. CVE-2026-32024 is fixed in 2026.2.22. Upgrade to this version or later.
5. Is CVE-2026-32024 exploitable, and should I be worried? Whether CVE-2026-32024 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32024 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32024? Upgrade openclaw to 2026.2.22 or later.