Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

OpenClaw has a path traversal in browser trace/download output paths may allow arbitrary file writes

CVE-2026-28462GHSA-gq9c-wg68-gwj2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.2.13), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    < 2026.2.13
    Fixed in
    2026.2.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · 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 · score source
EPSS
  • CVE-2026-28462: 0.48% estimated exploitation activity in the next 30 days; percentile 41.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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/stop - POST /wait/download - POST /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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-gq9c-wg68-gwj2

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-gq9c-wg68-gwj2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28462

Advisory: OpenClaw has a path traversal in browser trace/download output paths may allow arbitrary file writes
IDs: CVE-2026-28462, GHSA-gq9c-wg68-gwj2
Record: https://patchnext.com/advisories/cve-2026-28462 (revision 3, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.2.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected < 2026.2.13; fixed in 2026.2.13

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gq9c-wg68-gwj2 (OSV record GHSA-gq9c-wg68-gwj2 lists affected ranges: npm openclaw >=0 <2026.2.13 (fixed))
- Verified: https://github.com/advisories/GHSA-gq9c-wg68-gwj2 (GitHub-reviewed advisory GHSA-gq9c-wg68-gwj2 lists affected ranges: npm openclaw >=0 <2026.2.13)

Commands are suggestions: review each one before running it.

Loading voting…