How severe is GHSA-2858-xg23-26fp?

GHSA-2858-xg23-26fp has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2858-xg23-26fp?

GHSA-2858-xg23-26fp affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-2858-xg23-26fp?

Update openclaw to 2026.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2858-xg23-26fp is resolved across your whole dependency graph.

How do I detect GHSA-2858-xg23-26fp 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 GHSA-2858-xg23-26fp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2858-xg23-26fp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2858-xg23-26fp can be triaged on real exposure rather than presence alone.

Is GHSA-2858-xg23-26fp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2858-xg23-26fp 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.

When was GHSA-2858-xg23-26fp published, and has it been updated?

GHSA-2858-xg23-26fp was published on March 3, 2026 and was last updated on March 4, 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

MEDIUM severity

GHSA-2858-xg23-26fp — openclaw

MEDIUMFix: openclaw/openclaw@3bf19d6

GHSA-2858-xg23-26fp is a medium-severity (CVSS 5.5) vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw: Node camera URL payload host-binding bypass allowed gateway fetch pivots

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 4, 2026 · OSV.dev, 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

3.0Mdownloads / week

Description

Summary

OpenClaw accepted camera.snap / camera.clip node payload url fields and downloaded them on the gateway/agent host without binding downloads to the resolved node host.

In OpenClaw's documented trust model, paired nodes are in the same operator trust boundary, so this is scoped as medium-severity hardening. A malicious or compromised paired node could still steer gateway-host fetches during camera URL retrieval.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: >= 2026.2.13 <= 2026.3.1
Latest vulnerable published version at time of update: 2026.3.1
Patched versions: >= 2026.3.2 (released)

Technical Details

Vulnerable flows accepted URL payloads and downloaded directly from the provided URL:

src/cli/nodes-camera.ts (writeUrlToFile) fetched URL payloads without node-host binding.
src/cli/nodes-cli/register.camera.ts passed camera.snap / camera.clip payload URLs into that downloader.
src/agents/tools/nodes-tool.ts did the same for camera_snap / camera_clip tool actions.

Impact

A malicious/compromised paired node could cause gateway-host URL fetches to off-node destinations reachable from the host network. This could be used for internal network probing/fetch pivots in deployments where paired nodes are not fully trusted.

Remediation

The fix introduces fail-closed node-host binding and guarded fetch for camera URL payload downloads:

Require resolved node host metadata for URL payload downloads.
Enforce hostname match between payload URL and resolved node host.
Use SSRF-guarded fetch with redirect host/protocol checks.
Apply the same enforcement across CLI and agent tool camera paths.

Fix Commit(s)

3bf19d6f40a0aaa55818b96eede3d05130c02533

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.2.13&&< 2026.3.2	2026.3.2`npm install openclaw@2026.3.2`

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.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2858-xg23-26fp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2858-xg23-26fp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2858-xg23-26fp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary OpenClaw accepted `camera.snap` / `camera.clip` node payload `url` fields and downloaded them on the gateway/agent host without binding downloads to the resolved node host. In OpenClaw's documented trust model, paired nodes are in the same operator trust boundary, so this is scoped as medium-severity hardening. A malicious or compromised paired node could still steer gateway-host fetches during camera URL retrieval. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `>= 2026.2.13 <= 2026.3.1` - Latest vulnerable published version at time of update:

O3 Security · Impact-Aware SCA

Is GHSA-2858-xg23-26fp in your dependencies?

O3 Security finds GHSA-2858-xg23-26fp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works