CVE-2026-94633

Apache Thrift: Dart `TBinaryProtocol.readMessageBegin` allocates from the pre-versioned name length

Published Oct 2, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Dart bindings.



This issue affects Apache Thrift: before 0.25.0.



Users are recommended to upgrade to version 0.25.0, which fixes the issue.

Analysis

AI-generated

Technical impact

The flaw occurs in the Dart bindings of Apache Thrift, where the TBinaryProtocol.readMessageBegin function allocates memory based on a pre‑versioned name length. Because the length parameter is not properly validated, an attacker can send a crafted request that causes the function to allocate an excessive amount of memory. The resulting heap exhaustion or buffer overflow can crash the service, leading to a denial of service. The vulnerability is associated with typical size validation and allocation weaknesses and is identified by CWE-130, CWE-770, and CWE-789.

Affected Systems

Apache Thrift versions prior to 0.25.0 that use the Dart bindings are vulnerable. Any deployment exposing the Thrift Dart interface that has not applied the 0.25.0 release is at risk. The issue does not affect the Java or C++ bindings.

Risk and Exploitability

With a CVSS score of 8.7 the vulnerability poses a high risk. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Attackers can trigger the flaw by sending a malformed Thrift message over a network connection. Because the allocation depends on a length field that the server trusts, a remote client can instruct the server to allocate an arbitrarily large buffer or an invalid size, which can lead to out‑of‑memory errors or a crash. The exploitation requires the target to have the vulnerable Dart bindings exposed to untrusted input.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Apache Thrift Dart binding to version 0.25.0 or later, which applies the proper size‑validation logic.
  • Deploy network controls or API gateways that limit the size of Thrift traffic and reject oversized messages before they reach the server.
  • Configure the Thrift server to enforce stricter memory limits or runtime resource constraints, and monitor memory usage for abnormal spikes.

Generated by OpenCVE AI on October 2, 2026 at 14:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache
Apache thrift
Vendors & Products Apache
Apache thrift
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
Description Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift Dart bindings. This issue affects Apache Thrift: before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.
Title Apache Thrift: Dart `TBinaryProtocol.readMessageBegin` allocates from the pre-versioned name length
Weaknesses CWE-130
CWE-789
References
Metrics cvssV4_0

{'score': 8.7, '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'}

Weaknesses
  • CWE-130

    Improper Handling of Length Parameter Inconsistency

  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Oct 2, 2026, 11:28 AM
Reserved
Sep 21, 2026, 10:10 PM
Status
Deferred
Published
Oct 2, 2026, 11:17 AM
Modified
Oct 2, 2026, 2:30 PM
Severity
Important
Public date
Oct 2, 2026, 10:13 AM