dbcve.org
OpenclawApplication

CVE-2026-28461

HIGH · 7.5 CVSS v3.1 Published 2026-03-19
Fix available
A fix is available. Upgrade to 2026.3.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenClaw versions prior to 2026.3.1 contain an unbounded memory growth vulnerability in the Zalo webhook endpoint that allows unauthenticated attackers to trigger in-memory key accumulation by varying query strings. Remote attackers can exploit this by sending repeated requests with different query parameters to cause memory pressure, process instability, or out-of-memory conditions that degrade service availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OpenClaw versions prior to 2026.3.1 have an unbounded memory growth vulnerability in the Zalo webhook endpoint where unauthenticated attackers can accumulate in-memory keys by varying query string parameters, leading to memory exhaustion, process instability, or OOM conditions that degrade service availability.

MitigationImplement input validation to limit acceptable query parameters, add memory bounds and TTL/expiration for stored keys, and update to version 2026.3.1. Consider rate limiting on the webhook endpoint to further mitigate abuse.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenClaw version
    Locate the installed OpenClaw application and determine its version number. This is typically visible in the application banner, logs, or an About/Version endpoint.
    Affected if The installed version is prior to 2026.3.1 (for example, 2026.2.0, 2025.x, etc.)
  2. Identify Zalo webhook configuration
    Inspect the OpenClaw configuration files or admin interface to determine if the Zalo webhook endpoint has been enabled or configured.
    Affected if The Zalo webhook endpoint is enabled or configured in the environment
  3. Verify memory bounds on key storage
    Review the OpenClaw configuration or runtime settings for any memory bounds, TTL, or expiration settings applied to keys stored by the Zalo webhook endpoint.
    Affected if No memory bounds, TTL, or expiration are configured for keys stored by the webhook, allowing unlimited accumulation
  4. Test for unbounded query parameter storage
    Send multiple varied query string requests to the Zalo webhook endpoint while monitoring memory usage or observing if keys accumulate without cleanup.
    Affected if Memory usage grows unbounded or keys accumulate indefinitely as query parameters are varied

A user is affected if they are running OpenClaw version below 2026.3.1 with the Zalo webhook endpoint enabled and without memory bounds or TTL on stored keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.3.1 or later
Fixed in 2026.3.1
Interim mitigation

Implement input validation to limit acceptable query parameters, add memory bounds and TTL/expiration for stored keys, and update to version 2026.3.1. Consider rate limiting on the webhook endpoint to further mitigate abuse.

Recommended fix Moderate confidence

2026.3.1 or later

  1. 1. Identify the currently deployed Openclaw version using 'openclaw --version' or checking the application metadata
  2. 2. Review release notes for version 2026.3.1 to confirm the security fix addresses the Zalo webhook unbounded memory growth (CVE-2026-28461)
  3. 3. Create a backup of the current Openclaw configuration and data directory
  4. 4. Upgrade Openclaw to version 2026.3.1 or later using the standard upgrade procedure for your deployment method (e.g., package manager, container, or source compilation)
  5. 5. Verify the upgrade was successful by checking the new version number
  6. 6. Test the Zalo webhook endpoint functionality to ensure proper operation
  7. 7. Monitor memory usage after deployment to confirm the vulnerability is remediated
Caveat Review release notes for 2026.3.1; minor version upgrades may include configuration changes or dependency updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28461 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data