GHSA-j27p-hq53-9wgc is a high-severity (CVSS 7.5) CWE-770 vulnerability in openclaw. O3 Security confirms whether GHSA-j27p-hq53-9wgc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw affected by denial of service via unbounded URL-backed media fetch
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
openclawnpmDescription
Summary
URL-backed media fetch handling allocated the entire response payload in memory (arrayBuffer) before enforcing maxBytes, allowing oversized responses to cause memory exhaustion.
Affected Versions
openclaw(npm): <2026.2.14clawdbot(npm): <=2026.1.24-3
Patched Versions
openclaw(npm):2026.2.14
Fix Commit
openclaw/openclawmain:00a08908892d1743d1fc52e5cbd9499dd5da2fe0
Details
Affected component:
src/media/input-files.ts(fetchWithGuard)
When content-length is missing or incorrect, reading the body via response.arrayBuffer() buffers the full payload before a size check can run.
Proof of Concept
- Configure URL-based media input.
- Serve a response larger than
maxBytes(chunked transfer / nocontent-length). - Trigger the
fetchWithGuardURL fetch path.
Example local server (large response):
node -e 'require("http").createServer((_,res)=>{res.writeHead(200,{"content-type":"application/octet-stream"});for(let i=0;i<1024;i++)res.write(Buffer.alloc(1024*64));res.end();}).listen(18888)'
Impact
Availability loss via memory pressure from attacker-controlled remote media responses.
Mitigation
Until a patched release is available, disable URL-backed media inputs (or restrict to a tight hostname allowlist) and use conservative maxBytes limits.
Credits
Reported by @vincentkoc.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.14 |
Detection & mitigation playbook
Open-source dependencyDetect
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.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j27p-hq53-9wgc 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-j27p-hq53-9wgc 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-j27p-hq53-9wgc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j27p-hq53-9wgc in your dependencies?
O3 detects GHSA-j27p-hq53-9wgc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.