CVE-2026-83745

Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)

Published Oct 2, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift 
nodejs and D lang bindings.

Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the bytes have arrived. A single ~14-byte frame therefore commits as much memory as it cares to declare -- measured at 513 MiB against the Node.js server and 2 GiB against the D transport -- and in the Node.js case the connection is left open afterwards, so the frame can simply be sent again.




This issue affects Apache Thrift before 0.25.0.



Users are recommended to upgrade to version 0.25.0, which fixes the issue.

Analysis

AI-generated

Technical impact

A flaw in Apache Thrift’s WebSocket server transports causes the server to allocate a payload buffer based on the length field extracted from the frame header, without verifying that the declared number of bytes has actually been received. An attacker can send a frame that advertises a very large payload—up to 513 MiB in Node.js or 2 GiB in the D transport. The server immediately commits this memory, potentially exhausting the process or host resources and crashing or blocking the service. Because the connection remains open after the allocation in the Node.js binding, the attacker can repeatedly trigger the allocation, exacerbating the impact. This flaw falls under CWE‑130 (Improper Handling of Length Parameter Inconsistency) and CWE‑789 (Out-of-bounds Integer).

Affected Systems

The vulnerability affects Apache Thrift releases prior to version 0.25.0, specifically the Node.js and D language bindings that implement the WebSocket server transport. Any installation of Thrift that exposes a WebSocket endpoint using these bindings is impacted, regardless of the underlying operating system or runtime environment.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. The EPSS score is not available, but the issue is not listed in CISA’s KEV catalog, suggesting no publicly known exploits at this time. The likely attack vector is remote, via a malicious WebSocket client that can reach the server, and authentication is not required. The unchecked allocation makes the flaw trivial to trigger, giving the attacker a reliable path to cause denial of service or potentially assist in a larger denial or resource‑exhaustion attack.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Thrift to version 0.25.0 or later, which removes the unchecked buffer allocation.
  • If an upgrade cannot be performed immediately, limit inbound WebSocket traffic to trusted hosts using firewall rules or reverse‑proxy authentication to reduce the attack surface.
  • Configure system or application memory limits (e.g., cgroups or ulimit) for the Thrift process to contain potential memory over‑consumption and mitigate impact.

Generated by OpenCVE AI on October 2, 2026 at 13:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache
Apache thrift
Vendors & Products Apache
Apache thrift
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Redhat
Redhat hummingbird
CPEs cpe:/a:redhat:hummingbird:1
Vendors & Products Redhat
Redhat hummingbird
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
Description Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift  nodejs and D lang bindings. Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the bytes have arrived. A single ~14-byte frame therefore commits as much memory as it cares to declare -- measured at 513 MiB against the Node.js server and 2 GiB against the D transport -- and in the Node.js case the connection is left open afterwards, so the frame can simply be sent again. This issue affects Apache Thrift before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.
Title Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)
Weaknesses CWE-130
CWE-789
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-130

    Improper Handling of Length Parameter Inconsistency

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Oct 2, 2026, 5:16 PM
Reserved
Aug 31, 2026, 10:53 PM
Status
Deferred
Published
Oct 2, 2026, 1:17 PM
Modified
Oct 2, 2026, 6:17 PM
Severity
Important
Public date
Oct 2, 2026, 12:16 PM