How severe is CVE-2026-28467?

No CVSS score has been assigned to CVE-2026-28467 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-28467?

CVE-2026-28467 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-28467?

Update openclaw to 2026.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28467 is resolved across your whole dependency graph.

How do I detect CVE-2026-28467 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-28467 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2026-28467 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-28467 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-28467?

CVE-2026-28467 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-28467?

CVE-2026-28467 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-28467 published, and has it been updated?

CVE-2026-28467 was published on March 5, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-28467 — openclaw

Fix: openclaw/openclaw@81c68f5

CVE-2026-28467 is a Server-Side Request Forgery (SSRF) vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.2.2 - SSRF via Attachment Media URL Hydration

Also known asGHSA-wfp2-v9c7-fh79

Published

Mar 5, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-28467.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.5Mdownloads / week

Description

Summary

Versions of the openclaw npm package prior to 2026.2.2 could be coerced into fetching arbitrary http(s) URLs during attachment/media hydration. An attacker who can influence the media URL (for example via model-controlled sendAttachment or auto-reply media URLs) could trigger SSRF to internal resources and exfiltrate the fetched bytes as an outbound attachment.

Plain-English Explanation

OpenClaw can send files by downloading them first.

On vulnerable versions (< 2026.2.2), if an attacker could get OpenClaw to treat a URL as the “file to attach”, OpenClaw would download that URL from the gateway machine and then send the downloaded bytes back out as an attachment.

That matters because the gateway can often reach internal-only endpoints that an attacker cannot (for example 127.0.0.1 services, private RFC1918 addresses, or cloud metadata endpoints). This is a data-leak risk.

This does not directly grant code execution or shell access; it is about making the gateway perform HTTP requests and returning the response bytes.

Affected Packages / Versions

Package: openclaw (npm)
Affected: < 2026.2.2
Fixed: >= 2026.2.2

Release timeline (npm):

2026.2.1 published 2026-02-02T11:45:27Z
2026.2.2 published 2026-02-04T00:56:41Z
This advisory was created 2026-02-05T10:42:26Z

Details

In affected versions, remote media fetching performed a raw fetch(url) without SSRF protections.

Starting in 2026.2.2, remote media fetching is guarded by SSRF checks (private/loopback/link-local blocking, DNS pinning, and redirect handling), so attempts to fetch 127.0.0.1, private RFC1918 space, or cloud metadata hostnames are rejected.

Proof of Concept

From any context where an attacker can influence an attachment/media URL, provide a media URL targeting an internal endpoint (example: http://127.0.0.1:9999/secret.txt).

On vulnerable versions (< 2026.2.2), the gateway fetches the URL and uses the response bytes as the attachment payload.

Fix

Fix commits:

81c68f582d4a9a20d9cca9f367d2da9edc5a65ae
9bd64c8a1f91dda602afc1d5246a2ff2be164647

Mitigation

Upgrade to openclaw >= 2026.2.2.

Thanks @simecek for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.2`npm install openclaw@2026.2.2`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28467 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### Summary Versions of the `openclaw` npm package prior to `2026.2.2` could be coerced into fetching arbitrary `http(s)` URLs during attachment/media hydration. An attacker who can influence the media URL (for example via model-controlled `sendAttachment` or auto-reply media URLs) could trigger SSRF to internal resources and exfiltrate the fetched bytes as an outbound attachment. ### Plain-English Explanation OpenClaw can send files by downloading them first. On vulnerable versions (`< 2026.2.2`), if an attacker could get OpenClaw to treat a URL as the “file to attach”, OpenClaw would dow

O3 Security · Impact-Aware SCA

Is CVE-2026-28467 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works