OpenClaw has two SSRF via sendMediaFeishu and markdown image fetching in Feishu extension

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-28451: 0.32% estimated exploitation activity in the next 30 days; percentile 24.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The Feishu extension could fetch attacker-controlled remote URLs in two paths without SSRF protections: - sendMediaFeishu(mediaUrl) - Feishu DocX markdown image URLs (write/append - image processing) Affected versions - < 2026.2.14 Patched versions - = 2026.2.14 Impact If an attacker can influence tool calls (directly or via prompt injection), they may be able to trigger requests to internal services and re-upload the response as Feishu media. Remediation Upgrade to OpenClaw 2026.2.14 or newer. Notes The fix routes Feishu remote media fetching through hardened runtime helpers that enforce SSRF policies and size limits.

Published by the source

18 Feb 2026, 17:45 UTC

Last modified by the source

13 Mar 2026, 10:47 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x22m-j5qq-j49m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x22m-j5qq-j49m

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

# Patch Next advisory brief: CVE-2026-28451

Advisory: OpenClaw has two SSRF via sendMediaFeishu and markdown image fetching in Feishu extension
IDs: CVE-2026-28451, GHSA-x22m-j5qq-j49m
Record: https://patchnext.com/advisories/cve-2026-28451 (revision 2, 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.6)
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.14. A vendor fix does not mean a deployment is fixed.

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

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

Commands are suggestions: review each one before running it.