Skip to main content
VulnerabilityPublished Updated

CVE-2026-27488: Openclaw cli · OpenClaw hardened cron webhook delivery against SSRF

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.7.1 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.7.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.7.1.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • <2026.7.1
Fixed in
  • 2026.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied. Users should upgrade to version 2026.7.1 or later of the openclaw npm package where the SSRF vulnerability has been fixed. No additional mitigation steps are required beyond applying the official fix.

Description

The Openclaw CLI npm package versions up to 2026.2.17 contain a server-side request forgery (SSRF) vulnerability in the cron webhook delivery mechanism. The vulnerability arises because the code uses fetch() directly without SSRF policy checks, allowing webhook targets to access internal or private endpoints. This issue was fixed in versions after 2026.2.17 with specific commits addressing the problem.

References

Community reviews

Loading reviews…