# CVE-2026-83745: Apache Thrift memory exhaustion in WebSocket transports

Source: https://junglewise.ai/threats/cve-2026-83745-memory-allocation-with-excessive-size-value-improper-handling-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-83745 · Severity: info · Published 2026-10-02

Apache Thrift is an RPC framework used to build distributed systems. The Node.js and D language bindings contain a denial-of-service vulnerability where the WebSocket server transports allocate memory based on an unvalidated length field from incoming frames, allowing an attacker to exhaust server memory with a single small frame and crash the service.

Technologies: [Apache Thrift](https://junglewise.ai/threats/technologies/thrift). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-83745 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-83745 being exploited in the wild.

**How severe is CVE-2026-83745?** Informational severity, published 2 October 2026.

**Which products and versions are affected?** Apache Thrift before 0.25.0.

**Is there a fix for CVE-2026-83745?** Yes: fixed in 0.25.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-83745 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-83745?** Check whether you run Apache Thrift at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 0.25.0

## Technical details

The Node.js and D language WebSocket server transports read a payload length from the frame header and immediately allocate that amount of memory without validating that the declared bytes have actually arrived. An attacker can send a ~14-byte frame declaring a payload of 513 MiB (Node.js) or 2 GiB (D) to trigger excessive memory allocation. In the Node.js case, the connection remains open, enabling repeated attacks from the same source.

## Affected products

- Apache Thrift before 0.25.0

## Timeline

- 2026-10-02: disclosed

## References

- [https://registry.npmjs.org/](https://registry.npmjs.org/)
- [https://lists.apache.org/thread/33otcgbqd27wf6qq810q56znzbomnhg1](https://lists.apache.org/thread/33otcgbqd27wf6qq810q56znzbomnhg1)

## Related threats

- [Apache Thrift uncontrolled recursion in Java bindings](https://junglewise.ai/threats/cve-2026-120135-uncontrolled-recursion-vulnerability-in-apache-thrift-java)
- [Apache Thrift uncontrolled recursion in PHP bindings](https://junglewise.ai/threats/cve-2026-96289-uncontrolled-recursion-vulnerability-in-apache-thrift-php)
- [Apache Thrift Perl bindings inefficient algorithmic complexity](https://junglewise.ai/threats/cve-2026-96287-inefficient-algorithmic-complexity-vulnerability-in-apache-thrift)
- [Apache Thrift uncaught exception in Perl bindings](https://junglewise.ai/threats/cve-2026-96286-uncaught-exception-vulnerability-in-apache-thrift-perl-bindings)
- [Apache Thrift Ruby bindings exception handling vulnerability](https://junglewise.ai/threats/cve-2026-96277-uncaught-exception-improper-handling-of-exceptional-conditions)