CVE-2026-83745: CWE-789 Memory allocation with excessive size value in Apache Software Foundation Apache Thrift
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.
AI Analysis
Technical Summary
Apache Thrift versions prior to 0.25.0 contain a vulnerability in the Node.js and D language bindings' WebSocket server transports. These transports read the payload length from the frame header and allocate memory immediately without verifying that the full payload has arrived. This flaw allows a small frame (approximately 14 bytes) to cause the server to allocate an excessive amount of memory (up to 513 MiB on Node.js and 2 GiB on D transport). In the Node.js case, the connection remains open, allowing repeated exploitation. The vulnerability is addressed by upgrading to version 0.25.0.
Potential Impact
An attacker can cause the affected Apache Thrift WebSocket servers to allocate excessive memory, leading to resource exhaustion and potential denial of service. The Node.js binding is particularly vulnerable as it keeps the connection open after the attack frame, enabling repeated exploitation. This can disrupt service availability and degrade system performance.
Mitigation Recommendations
Users should upgrade Apache Thrift to version 0.25.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
CVE-2026-83745: CWE-789 Memory allocation with excessive size value in Apache Software Foundation Apache Thrift
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.
CVSS v4.0
Score 8.7high
Affected software
Apache Software Foundation
Apache Thrift
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache Thrift versions prior to 0.25.0 contain a vulnerability in the Node.js and D language bindings' WebSocket server transports. These transports read the payload length from the frame header and allocate memory immediately without verifying that the full payload has arrived. This flaw allows a small frame (approximately 14 bytes) to cause the server to allocate an excessive amount of memory (up to 513 MiB on Node.js and 2 GiB on D transport). In the Node.js case, the connection remains open, allowing repeated exploitation. The vulnerability is addressed by upgrading to version 0.25.0.
Potential Impact
An attacker can cause the affected Apache Thrift WebSocket servers to allocate excessive memory, leading to resource exhaustion and potential denial of service. The Node.js binding is particularly vulnerable as it keeps the connection open after the attack frame, enabling repeated exploitation. This can disrupt service availability and degrade system performance.
Mitigation Recommendations
Users should upgrade Apache Thrift to version 0.25.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-08-31T22:53:07.156Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abfa42aa43b0b3b89b87d66
Added to database: 10/02/2026, 12:31:38 UTC
Last enriched: 10/02/2026, 12:46:48 UTC
Last updated: 10/03/2026, 04:45:56 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.