CVE-2026-28393
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 2.0.0-beta3 prior to 2026.2.14 contain a path traversal vulnerability in hook transform module loading that allows arbitrary JavaScript execution. The hooks.mappings[].transform.module parameter accepts absolute paths and traversal sequences, enabling attackers with configuration write access to load and execute malicious modules with gateway process privileges.
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 · high confidenceOpenClaw versions 2.0.0-beta3 before 2026.2.14 contain a path traversal vulnerability in the hook transform module loading mechanism. The hooks.mappings[].transform.module parameter accepts absolute paths and traversal sequences (e.g., ../../../malicious.js), allowing attackers with configuration write access to load and execute arbitrary JavaScript modules with gateway process privileges.
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.1.4, < 2026.2.14= 2.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed OpenClaw versionLocate the OpenClaw version information (typically via CLI command, package metadata, or version file) and compare it to the affected ranges: >= 2026.1.4, < 2026.2.14 or version 2.0.0Affected if Version falls within the affected ranges (2026.1.4 through 2026.2.13, or exactly 2.0.0)
-
Locate hooks configurationFind the configuration file containing hook mappings (commonly named hooks.json, hooks.yaml, or similar in the OpenClaw config directory)Affected if A hooks configuration file exists in the environment
-
Inspect transform module pathsOpen the hooks configuration file and examine the transforms.module field under each entry in the mappings array for path traversal sequences such as ../, ./, or absolute paths pointing outside the intended modules directoryAffected if Any transform.module value contains relative path traversal sequences (e.g., ../../../) or absolute paths pointing to unexpected locations
-
Verify configuration file permissionsCheck file system permissions on the hooks configuration file to determine if untrusted users or processes have write accessAffected if The configuration file is writable by users or processes that should not have modification privileges
Environment is affected if OpenClaw version is within the vulnerable range AND hooks configuration with transform.module paths exists containing path traversal sequences, combined with writable configuration access by untrusted actors.
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.2.14
Upgrade to OpenClaw 2026.2.14 or later, which contains the security fix. Additionally, restrict write access to configuration files and implement path validation to prevent traversal sequences in module paths.
2026.2.14
- Upgrade OpenClaw to version 2026.2.14 or later to obtain the patched code
- If running in production, test the upgrade in a staging environment first
- After upgrading, verify that the hooks.mappings[].transform.module parameter properly rejects absolute paths and traversal sequences like '../'
- Review access controls around configuration write access to prevent attackers from exploiting this path traversal vector
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-28393 — 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-28393 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