Skip to content
Noroxi
OSV ecosystem advisory

GHSA-2858-xg23-26fp: OpenClaw: Node camera URL payload host-binding bypass allowed gateway fetch pivots

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: openclaw (npm) 2026.3.2.

Low priority for now. Upgrade to openclaw (npm) 2026.3.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: OSV

### 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`

Published
Mar 3, 2026
Updated
Mar 4, 2026
EPSS
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow GHSA-2858-xg23-26fp

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
npmopenclaw

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmopenclawfrom 2026.2.13 · before 2026.3.22026.3.2

Same product

npm: all records

Other highest-scoring records for the same primary product.

  • GHSA-943q-mwmv-hhvhOpenClaw: Gateway /tools/invoke tool escalation + ACP permission auto-approval
    35Monitor
  • GHSA-474h-prjg-mmw3OpenClaw: Sandboxed sessions_spawn(runtime="acp") bypassed sandbox inheritance and allowed host ACP initialization
    32Monitor
  • GHSA-56f2-hvwg-5743OpenClaw affected by SSRF in Image Tool Remote Fetch
    30Monitor

Published before and after this one in the same product

  • ← EarlierGHSA-h656-5vcf-cm23Mar 3, 2026 · OpenClaw: Unauthorized Telegram Senders Trigger Media Download and Disk Write Before Access Check
    0Monitor
  • ← EarlierGHSA-qhrr-grqp-6x2gMar 3, 2026 · OpenClaw's tools.exec.safeBins trusted PATH directories allowed binary shadowing in allowlist mode
    0Monitor
  • Later →GHSA-2mc2-g238-722jMar 3, 2026 · OpenClaw affected by iMessage remote attachment SCP hardening (strict host-key checks and remoteHost validation)
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
npm:openclaw2026.3.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • GHSA-56f2-hvwg-574314 days apartOpenClaw affected by SSRF in Image Tool Remote Fetch
    30Monitor
  • GHSA-h97f-6pqj-q4520 days apartOpenClaw has a IPv6 multicast SSRF classifier bypass
    0Monitor
  • GHSA-8cp7-rp8r-mg771 days apartOpenClaw has SSRF guard bypass via IPv6 transition over ISATAP
    0Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • GHSA-4cqv-h74h-93j40 days apartOpenClaw has a Discord `allowFrom` slug-collision authorization bypass
    26Monitor
  • GHSA-gcj7-r3hg-m7w60 days apartOpenClaw's voice-call Twilio replay dedupe now bound to authenticated webhook identity
    14Monitor
  • GHSA-2hm8-rqrm-xfjq0 days apartOpenClaw's owner-only gateway tool access checks were incomplete in specific authenticated DM flows
    0Monitor
  • GHSA-pfv7-rr5m-qmv60 days apartOpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
    0Monitor

Not on record for this CVE: EPSS history · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

osv

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records