Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 1.7amended

OpenClaw: Isolated cron awareness events were recorded as trusted system events

CVE-2026-44999GHSA-57r2-h2wj-g887

What to do

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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
1.7 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U · score source
EPSS
  • CVE-2026-44999: 0.15% estimated exploitation activity in the next 30 days; percentile 4.29 (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.

Affected Packages / Versions - Package: openclaw (npm) - Affected versions: < 2026.4.20 - Patched version: 2026.4.20 Impact Output from webhook-triggered isolated cron agent runs could be queued into the main session awareness stream without trusted: false. That made the event render as a trusted System: event instead of an untrusted system event. This is a trust-labeling issue that can strengthen prompt-injection impact, but it does not directly bypass gateway auth, tool policy, or sandboxing. Severity is low. Fix OpenClaw now preserves untrusted labels for isolated cron awareness events and forwards the trust flag through cron delivery helpers. Fix commit: - f61896b03cc7031f51106a04566831f4ac2a0bd7 Release Fixed in OpenClaw 2026.4.20.

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

    Amended from ghsa record GHSA-57r2-h2wj-g887

  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-57r2-h2wj-g887

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

Advisory: OpenClaw: Isolated cron awareness events were recorded as trusted system events
IDs: CVE-2026-44999, GHSA-57r2-h2wj-g887
Record: https://patchnext.com/advisories/cve-2026-44999 (revision 3, 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: Low (CVSS 1.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.4.20. A vendor fix does not mean a deployment is fixed.

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

## 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-57r2-h2wj-g887 (OSV record GHSA-57r2-h2wj-g887 lists affected ranges: npm openclaw >=0 <2026.4.20 (fixed))
- Verified: https://github.com/advisories/GHSA-57r2-h2wj-g887 (GitHub-reviewed advisory GHSA-57r2-h2wj-g887 lists affected ranges: npm openclaw >=0 <2026.4.20)

Commands are suggestions: review each one before running it.

Loading voting…