CVE-2026-83745 json
Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)
published last mo. modified last mo. also BIT-thrift-2026-83745 , EUVD-2026-91580
- cvss
- 8.7
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami thrift 0.25.0
- Apache Software Foundation Apache Thrift 0.25.0
- thrift hummingbird 1 0.25.0-0.1.hum1
- thrift-qt hummingbird 1 0.25.0-0.1.hum1
- perl-thrift hummingbird 1 0.25.0-0.1.hum1
- thrift-glib hummingbird 1 0.25.0-0.1.hum1
- python3-thrift hummingbird 1 0.25.0-0.1.hum1
red hat advisories RHSA-2026:74369
- thrift Azure Linux 3.0 0.25.0-1
azure linux advisories AZL-105953
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Is CVE-2026-83745 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-83745 updated cvss 7.5
thrift: thrift: Denial of Service via excessive memory allocation in WebSocket transport
-
Red Hat Ceph Storage 7 thrift Red Hat Ceph Storage 8 thrift, thrift-qt, perl-thrift, thrift-glib, python3-thrift Red Hat Ceph Storage 9 thriftaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux AI (RHEL AI) 3 thriftaffected: workaround, no fix available
-
Red Hat Hardened Images thrift 0.25.0-0.1.hum1, thrift-qt 0.25.0-0.1.hum1, perl-thrift 0.25.0-0.1.hum1, thrift-glib 0.25.0-0.1.hum1, python3-thrift 0.25.0-0.1.hum1fixed: vendor fix RHSA-2026:74369
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.7 | 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 |
| CNA | 4.0 | 8.7 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | thrift | <0.25.0 |
0.25.0 |
Affected products
- Apache Software Foundation Apache Thrift
Classification
References
-
lists.apache.org
/thread/33otcgbqd27wf6qq810q56znzbomnhg1
vendor-advisory, web
-
lists.apache.org
/thread/64y7f0b89mnq4xoqcn4h26to8kskolgc
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-83745
web
Sources
- CVE List CVE-2026-83745
- NVD CVE-2026-83745
- OSV BIT-thrift-2026-83745
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.