Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.2amended

OpenClaw: Gateway HTTP endpoints re-resolve bearer auth after SecretRef rotation

CVE-2026-43585GHSA-xmxx-7p24-h892

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.4.15), 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.4.15
    Fixed in
    2026.4.15

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.2 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-43585: 0.54% estimated exploitation activity in the next 30 days; percentile 45.51 (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 Gateway HTTP and WebSocket handlers captured the resolved bearer-auth configuration when the server started. After a SecretRef rotation, the already-running gateway could continue accepting the old bearer token until restart. Impact A bearer token that should have been revoked by SecretRef rotation could remain valid on the gateway HTTP and upgrade surfaces for the lifetime of the process. Severity remains high because the old token could continue to authorize gateway requests after operators believed it was rotated out. Affected versions - Affected: < 2026.4.15 - Patched: 2026.4.15 Fix OpenClaw 2026.4.15 resolves active gateway auth from the runtime secret snapshot per request and per upgrade instead of using a stale startup-time value. Verified in v2026.4.15: - src/gateway/server.impl.ts exposes getResolvedAuth() backed by the current runtime secret snapshot. - src/gateway/server-http.ts calls getResolvedAuth() for each HTTP request and WebSocket upgrade before running auth…

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

    Amended from ghsa record GHSA-xmxx-7p24-h892

  2. Revision 3 · amended ·

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

  3. Revision 2 · amended ·

    Amended from osv record GHSA-xmxx-7p24-h892

  4. Revision 1 · created ·

    Published from ghsa record GHSA-xmxx-7p24-h892

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-43585

Advisory: OpenClaw: Gateway HTTP endpoints re-resolve bearer auth after SecretRef rotation
IDs: CVE-2026-43585, GHSA-xmxx-7p24-h892
Record: https://patchnext.com/advisories/cve-2026-43585 (revision 4, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.4.15. A vendor fix does not mean a deployment is fixed.

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

## 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://github.com/advisories/GHSA-xmxx-7p24-h892 (GitHub-reviewed advisory GHSA-xmxx-7p24-h892 lists affected ranges: npm openclaw >=0 <2026.4.15)
- Verified: https://osv.dev/vulnerability/GHSA-xmxx-7p24-h892 (OSV record GHSA-xmxx-7p24-h892 lists affected ranges: npm openclaw >=0 <2026.4.15 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…