How severe is GHSA-h656-5vcf-cm23?

No CVSS score has been assigned to GHSA-h656-5vcf-cm23 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h656-5vcf-cm23?

GHSA-h656-5vcf-cm23 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-h656-5vcf-cm23?

Update openclaw to 2026.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h656-5vcf-cm23 is resolved across your whole dependency graph.

How do I detect GHSA-h656-5vcf-cm23 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h656-5vcf-cm23 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-h656-5vcf-cm23?

O3 pinpoints whether GHSA-h656-5vcf-cm23 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h656-5vcf-cm23 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h656-5vcf-cm23 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-h656-5vcf-cm23 published, and has it been updated?

GHSA-h656-5vcf-cm23 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

GHSA-h656-5vcf-cm23

OpenClaw: Unauthorized Telegram Senders Trigger Media Download and Disk Write Before Access Check

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Impact

In Telegram DM mode, inbound media was downloaded and written to disk before sender authorization checks completed. An unauthorized sender could trigger inbound media download/write activity (including media groups) even when DM access should be denied.

Affected Packages / Versions

Package: openclaw (npm)
Latest published version currently affected: 2026.2.23
Vulnerable range: <= 2026.2.23
Patched in planned next release: 2026.2.24

Fix Commit(s)

9514201fb9b51de5d0b23151110d0ff5d9c8bd67

Technical Details

The Telegram handler flow now enforces DM authorization before media download/write paths execute, including media-group handling. Inbound channel activity tracking was also moved to run after DM authorization in the Telegram message context path.

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.24). After npm publish, the advisory can be published without further version-field edits.

OpenClaw thanks @v8hid for reporting.

Publication Update (2026-02-25)

[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.24

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h656-5vcf-cm23 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 pinpoints whether GHSA-h656-5vcf-cm23 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h656-5vcf-cm23. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Impact In Telegram DM mode, inbound media was downloaded and written to disk before sender authorization checks completed. An unauthorized sender could trigger inbound media download/write activity (including media groups) even when DM access should be denied. ## Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version currently affected: `2026.2.23` - Vulnerable range: `<= 2026.2.23` - Patched in planned next release: `2026.2.24` ## Fix Commit(s) - `9514201fb9b51de5d0b23151110d0ff5d9c8bd67` ## Technical Details The Telegram handler flow now enforces DM aut

O3 Security · Impact-Aware SCA

Is GHSA-h656-5vcf-cm23 in your dependencies?

O3 detects GHSA-h656-5vcf-cm23 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works