GHSA-GQ9C-WG68-GWJ2
Vulnerability from github – Published: 2026-02-18 17:38 – Updated: 2026-03-06 01:04Summary
OpenClaw’s browser control API accepted user-supplied output paths for trace/download files without consistently constraining writes to OpenClaw-managed temporary directories.
## Impact
If an attacker can access the browser control API, they could attempt to write trace/download output files outside intended temp roots, depending on process filesystem permissions.
## Affected versions
openclaw < 2026.2.13
## Fixed versions
openclaw >= 2026.2.13
## Remediation
Upgrade to 2026.2.13 or later.
## What changed
The fix constrains output paths for:
POST /trace/stopPOST /wait/downloadPOST /download
All three now enforce OpenClaw temp-root boundaries and reject traversal/escape paths.
## Credits
Thanks to Adnan Jakati (@jackhax) of Praetorian for responsible disclosure.
Fix shipped in PR #15652 and merged to main on February 13, 2026 (7f0489e4731c8d965d78d6eac4a60312e46a9426).
Fix commit 7f0489e4731c8d965d78d6eac4a60312e46a9426 confirmed on main and in v2026.2.14. Upgrade to openclaw >= 2026.2.13.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "openclaw"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2026.2.13"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-28462"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-18T17:38:39Z",
"nvd_published_at": "2026-03-05T22:16:18Z",
"severity": "HIGH"
},
"details": "## Summary\n\n OpenClaw\u2019s browser control API accepted user-supplied output paths for trace/download files without consistently\n constraining writes to OpenClaw-managed temporary directories.\n\n ## Impact\n\n If an attacker can access the browser control API, they could attempt to write trace/download output files outside\n intended temp roots, depending on process filesystem permissions.\n\n ## Affected versions\n\n `openclaw` `\u003c 2026.2.13`\n\n ## Fixed versions\n\n `openclaw` `\u003e= 2026.2.13`\n\n ## Remediation\n\n Upgrade to `2026.2.13` or later.\n\n ## What changed\n\n The fix constrains output paths for:\n\n - `POST /trace/stop`\n - `POST /wait/download`\n - `POST /download`\n\n All three now enforce OpenClaw temp-root boundaries and reject traversal/escape paths.\n\n ## Credits\n\n Thanks to Adnan Jakati (@jackhax) of Praetorian for responsible disclosure.\n\n Fix shipped in PR #15652 and merged to `main` on February 13, 2026 (`7f0489e4731c8d965d78d6eac4a60312e46a9426`).\n\n---\n\nFix commit 7f0489e4731c8d965d78d6eac4a60312e46a9426 confirmed on main and in v2026.2.14. Upgrade to `openclaw \u003e= 2026.2.13`.",
"id": "GHSA-gq9c-wg68-gwj2",
"modified": "2026-03-06T01:04:42Z",
"published": "2026-02-18T17:38:39Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-gq9c-wg68-gwj2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-28462"
},
{
"type": "WEB",
"url": "https://github.com/openclaw/openclaw/pull/15652"
},
{
"type": "WEB",
"url": "https://github.com/openclaw/openclaw/commit/7f0489e4731c8d965d78d6eac4a60312e46a9426"
},
{
"type": "PACKAGE",
"url": "https://github.com/openclaw/openclaw"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/openclaw-path-traversal-in-trace-and-download-output-paths"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "OpenClaw has a path traversal in browser trace/download output paths may allow arbitrary file writes"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.