Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.0amended

OpenClaw's Webhooks SecretRef route secret remains valid after rotation/reload

CVE-2026-45005GHSA-q8ff-7ffm-m3r9

What to do

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.0 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:L
EPSS
  • CVE-2026-45005: 0.29% estimated exploitation activity in the next 30 days; percentile 21.48 (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 webhooks allowed route secrets to be backed by SecretRef values, but cached the resolved secret for a route. After an operator rotated the underlying secret and ran openclaw secrets reload, the previous resolved webhook secret could remain valid until the plugin or gateway restarted. Impact An attacker who already had a previously valid webhook route secret could continue authenticating webhook requests after the operator rotated the secret and reloaded secrets. This weakened credential rotation for webhook routes and could allow continued invocation of the configured webhook task flow until restart. Affected Packages / Versions - Package: openclaw on npm - Affected: versions before 2026.4.23 - Fixed: 2026.4.23 - Latest stable verified fixed: openclaw@2026.4.23, tag v2026.4.23 Fix Webhook route authentication now resolves SecretRef-backed route secrets on each request. A rotated secret becomes effective after openclaw secrets reload without requiring a gateway or…

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

    Amended from ghsa record GHSA-q8ff-7ffm-m3r9

  2. Revision 1 · created ·

    Published from osv record GHSA-q8ff-7ffm-m3r9

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

Advisory: OpenClaw's Webhooks SecretRef route secret remains valid after rotation/reload
IDs: CVE-2026-45005, GHSA-q8ff-7ffm-m3r9
Record: https://patchnext.com/advisories/cve-2026-45005 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
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.23. A vendor fix does not mean a deployment is fixed.

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

## 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-q8ff-7ffm-m3r9 (OSV record GHSA-q8ff-7ffm-m3r9 lists affected ranges: npm openclaw >=0 <2026.4.23 (fixed))
- Verified: https://github.com/advisories/GHSA-q8ff-7ffm-m3r9 (GitHub-reviewed advisory GHSA-q8ff-7ffm-m3r9 lists affected ranges: npm openclaw >=0 <2026.4.23)

Commands are suggestions: review each one before running it.

Loading voting…