Skip to content
VulniPulse
High 2 vendors · 2 advisories

CVE-2026-83745: Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)

CVE-2026-83745 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
8.7 (Apache), 7.5 (Red Hat)
CVSS vector
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 · base score 8.7, scored by apacheAttack vector: network. Attack complexity: low. Attack requirements: none. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: none. Integrity impact on the vulnerable system: none. Availability impact on the vulnerable system: high. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-789 Memory allocation with excessive size value
  • CWE-130 Improper handling of length parameter inconsistency
EPSS
0.34% chance of exploitation in the next 30 days (28th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
Fixed releases
  • Apache: 0.25.0
  • Red Hat: 0.25.0, thrift-main-0.25.0-0.1.hum1, RHSA-2026:74369
Vendor advisories
2 from Apache, Red Hat
Assigned by
apache (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-83745; each belongs to its advisory, not to every product listed. How records are collected and checked.

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.

Text from the CVE.org record (apache).

How do I fix CVE-2026-83745?

Upgrade to a fixed release named by the vendor:

  • Apache: 0.25.0
  • Red Hat: 0.25.0, thrift-main-0.25.0-0.1.hum1, RHSA-2026:74369
  • Users are recommended to upgrade to version 0.25.0, which fixes the issue. (Apache)
  • Restrict network reachability to services exposing Apache Thrift WebSocket transports by limiting access to trusted IP addresses or binding exclusively to the loopback interface. 1. If remote access is not required, configure the application to listen only on localhost (127.0.0.1). 2. To restrict exposure using firewalld, remove the service port from public zones and allow access only from trusted IP subnets: firewall-cmd --permanent --zone=public --remove-port= /tcp firewall-cmd --permanent --zone=trusted --add-source= firewall-cmd --permanent --zone=trusted --add-port= /tcp firewall-cmd --reload Caveat: Restricting network access prevents legitimate clients outside of the trusted subnet from connecting to the service. Warning: Executing 'firewall-cmd --reload' applies configuration changes immediately and may disrupt active network connections. (Red Hat)

Vendor advisories for CVE-2026-83745

Apache

1 advisory
  • Advisory severityHigh8.7

    High [CVE-2026-83745] Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift nodejs and D lang bindings

    CVE-2026-83745Source published Source updated

    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.

    Affected products in this advisory
    • Apache Thrift
    Source-reported affected versions
    • Apache Thrift before 0.25.0
    Source-reported fixed versions
    • 0.25.0
    Mitigation guidance
    • Users are recommended to upgrade to version 0.25.0, which fixes the issue.

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-83745] Denial of Service via excessive memory allocation in WebSocket transport

    CVE-2026-83745Source published Source updated

    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. A remote attacker can cause a Denial of Service (DoS) against the…

    Affected products in this advisory
    • Red Hat Hardened Images
    • Red Hat Ceph Storage 7
    • Red Hat Ceph Storage 8
    • Red Hat Ceph Storage 9

    1 more entries in the full advisory.

    Source-reported affected versions
    • < 0.25.0
    Source-reported fixed versions
    • 0.25.0
    • thrift-main-0.25.0-0.1.hum1
    • RHSA-2026:74369
    Mitigation guidance
    • Restrict network reachability to services exposing Apache Thrift WebSocket transports by limiting access to trusted IP addresses or binding exclusively to the loopback interface. 1. If remote access is not required, configure the application to listen only on localhost (127.0.0.1). 2. To restrict exposure using firewalld, remove the service port from public zones and allow access only from trusted IP subnets: firewall-cmd --permanent --zone=public --remove-port=<PORT>/tcp firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_CIDR> firewall-cmd --permanent --zone=trusted --add-port=<PORT>/tcp firewall-cmd --reload Caveat: Restricting network access prevents legitimate clients outside of the trusted subnet from connecting to the service. Warning: Executing 'firewall-cmd --reload' applies configuration changes immediately and may disrupt active network connections.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache