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
The vulnerability in Apache Thrift nodejs and D lang bindings arises from the WebSocket server transports reading the payload length from the frame header and allocating memory accordingly without confirming the actual arrival of the data. This allows an attacker to send a small frame (~14 bytes) that declares a very large payload length, causing the server to allocate excessive memory (up to 513 MiB in nodejs and 2 GiB in D transport). In the nodejs case, the connection remains open, allowing repeated exploitation. This flaw is present in Apache Thrift versions prior to 0.25.0 and is addressed in the 0.25.0 release.
Potential Impact
The vulnerability can lead to excessive memory allocation on affected Apache Thrift servers, potentially causing denial of service by exhausting system memory resources. The nodejs binding is particularly vulnerable as the connection remains open after the large allocation, allowing repeated exploitation. This can degrade service availability and stability.
Mitigation Recommendations
Users should upgrade Apache Thrift to version 0.25.0 or later, where this issue is fixed. No other mitigation is indicated. Patch status is confirmed by the vendor advisory recommending upgrade to 0.25.0.
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
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
The vulnerability in Apache Thrift nodejs and D lang bindings arises from the WebSocket server transports reading the payload length from the frame header and allocating memory accordingly without confirming the actual arrival of the data. This allows an attacker to send a small frame (~14 bytes) that declares a very large payload length, causing the server to allocate excessive memory (up to 513 MiB in nodejs and 2 GiB in D transport). In the nodejs case, the connection remains open, allowing repeated exploitation. This flaw is present in Apache Thrift versions prior to 0.25.0 and is addressed in the 0.25.0 release.
Potential Impact
The vulnerability can lead to excessive memory allocation on affected Apache Thrift servers, potentially causing denial of service by exhausting system memory resources. The nodejs binding is particularly vulnerable as the connection remains open after the large allocation, allowing repeated exploitation. This can degrade service availability and stability.
Mitigation Recommendations
Users should upgrade Apache Thrift to version 0.25.0 or later, where this issue is fixed. No other mitigation is indicated. Patch status is confirmed by the vendor advisory recommending upgrade to 0.25.0.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-5jgj-9r28-q5fp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-83745"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6abfee77a43b0b3b89e54386
Added to database: 10/02/2026, 17:48:39 UTC
Last enriched: 10/02/2026, 17:51:41 UTC
Last updated: 10/03/2026, 02:45:56 UTC
Views: 3
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.