Denial of Service Vulnerability in OpenClaw: Memory Pressure from Large Base64 Media Files

openclaw Updated 18 Feb 2026

Summary

18/02/2026
MODERATE
Yes i
Moderate
5.5

GHSA-w2cg-vxx6-5xjg: Base64-backed media inputs could be decoded into Buffers before enforcing decoded-size budgets. Affects openclaw versions < 2026.2.14. Fixed in 2026.2.14. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

OpenClaw is an npm package designed for handling media inputs, particularly those encoded in base64 format. It allows developers to easily integrate media handling capabilities into their applications. However, due to its handling of base64 inputs, OpenClaw is susceptible to vulnerabilities that can lead to denial of service (DoS) attacks, particularly when large payloads are processed without proper size checks.

Vulnerability Detail

The vulnerability arises from the way OpenClaw decodes base64-encoded media inputs into Buffers before enforcing size limits. An attacker can exploit this by supplying oversized base64 payloads, which can lead to excessive memory allocation, causing memory pressure and potentially crashing the application. This vulnerability is particularly concerning if the gateway is exposed to untrusted networks, as it can be exploited remotely, increasing the severity of the risk.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.14

This is the first release that contains the fix.

npm install openclaw@2026.2.14

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, consider binding the gateway to loopback and enforcing authentication for HTTP endpoints to mitigate the risk of unauthorized access and potential DoS attacks.

Conclusion

The OpenClaw package has a vulnerability that allows for denial of service through large base64 media files. It is crucial to update to the patched version to mitigate this risk. Additionally, implementing workarounds can help protect your application until an update can be applied.

See every vulnerability recorded for openclaw →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 5.5, indicating a moderate severity level.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If exploited, this vulnerability can lead to denial of service, causing your application to become unresponsive or crash due to excessive memory usage.

No, there is no patched release planned for clawdbot. It is recommended to migrate to OpenClaw to mitigate the risk.

If immediate updates are not possible, ensure that your gateway is bound to loopback and that you have strong authentication and rate limiting in place to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for openclaw.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.2.14

This is the first release that contains the fix.

npm install openclaw@2026.2.14

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.