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