CVE-2026-32980 | OpenClaw up to 2026.3.12 JSON Parser allocation of resources (GHSA-jq3f-vjww-8rq7)

VDB-354114 · CVE-2026-32980 · GHSA-JQ3F-VJWW-8RQ7 OPENCLAW UP TO 2026.3.12 JSON PARSER ALLOCATION OF RESOURCES HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.3 $0-$5k 1.04+ Summaryinfo A vulnerability described as problematic has been identified in OpenClaw up to 2026.3.12. This affects an unknown part of the component JSON Parser. The manipulation results in allocation of resources. This vulnerability is cataloged as CVE-2026-32980. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is recommended. Detailsinfo A vulnerability classified as problematic has been found in OpenClaw up to 2026.3.12. Affected is an unknown code block of the component JSON Parser. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. CVE summarizes: OpenClaw before 2026.3.13 reads and buffers Telegram webhook request bodies before validating the x-telegram-bot-api-secret-token header, allowing unauthenticated attackers to exhaust server resources. Attackers can send POST requests to the webhook endpoint to force memory consumption, socket time, and JSON parsing work before authentication validation occurs. The advisory is available at github.com. This vulnerability is traded as CVE-2026-32980 since 03/17/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project. Upgrading to version 2026.3.13 eliminates this vulnerability. Applying the patch 7e49e98f79073b11134beac27fdff547ba5a4a02 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Type Artificial Intelligence Software Name OpenClaw Version 2026.3.0 2026.3.1 2026.3.2 2026.3.3 2026.3.4 2026.3.5 2026.3.6 2026.3.7 2026.3.8 2026.3.9 2026.3.10 2026.3.11 2026.3.12 License open-source Website Product: https://github.com/openclaw/openclaw/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 6.4 VulDB Meta Temp Score: 6.3 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Allocation of resources CWE: CWE-770 / CWE-400 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: OpenClaw 2026.3.13 Patch: 7e49e98f79073b11134beac27fdff547ba5a4a02 Timelineinfo 03/17/2026 CVE reserved 03/29/2026 +12 days Advisory disclosed 03/29/2026 +0 days VulDB entry created 03/29/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-jq3f-vjww-8rq7 Status: Confirmed CVE: CVE-2026-32980 (🔒) GCVE (CVE): GCVE-0-2026-32980 GCVE (VulDB): GCVE-100-354114 Entryinfo Created: 03/29/2026 17:49 Changes: 03/29/2026 17:49 (78) Complete: 🔍 Cache ID: 99:404:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸