CVE-2026-66054

Apache Thrift: C++ THeaderTransport does not enforce configured maxFrameSize

Published Oct 2, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
Allocation of Resources Without Limits or Throttling, Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Thrift C++ 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 C++ implementation of Apache Thrift’s THeaderTransport does not enforce the configured maxFrameSize value, causing the library to allocate memory for an incoming request before rejecting it. An attacker can therefore send a request larger than the intended frame size and trigger the allocation of an excessive amount of memory or other system resources, which can exhaust those resources and result in a denial of service. The flaw is a resource exhaustion weakness, classified as CWE-409 and CWE-770, and it primarily impacts availability without directly compromising confidentiality or integrity.

Affected Systems

This vulnerability is present in all Apache Thrift releases prior to version 0.25.0, affecting the C++ bindings that use THeaderTransport. Any deployment of Thrift before that version that does not apply the vendor patch is susceptible. The affected product is Apache Thrift released by the Apache Software Foundation.

Risk and Exploitability

The vulnerability has a CVSS score of 6.9, indicating moderate to high severity. The EPSS score is not available, meaning there is insufficient data on the likelihood of exploitation in the wild. The issue is not listed in the CISA KEV catalog, further suggesting that widespread exploitation is not known. The attack vector is likely remote, as an attacker can trigger the flaw by sending specially crafted requests over the network to a Thrift service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Thrift to version 0.25.0 or later to apply the vendor fix.
  • Set a realistic maxFrameSize value in THeaderTransport configuration and enforce it in all servers using the Thrift C++ bindings.
  • Apply operating‑system resource limits such as cgroups or ulimit to bound the memory usage of the Thrift process, reducing the impact if an upgrade cannot be applied immediately.

Generated by OpenCVE AI on October 2, 2026 at 15:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Redhat
Redhat hummingbird
CPEs cpe:/a:redhat:hummingbird:1
Vendors & Products Redhat
Redhat hummingbird
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
First Time appeared Apache
Apache thrift
Vendors & Products Apache
Apache thrift
Type Values Removed Values Added
Description Allocation of Resources Without Limits or Throttling, Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in Apache Thrift C++ 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: C++ THeaderTransport does not enforce configured maxFrameSize
Weaknesses CWE-409
CWE-770
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-409

    Improper Handling of Highly Compressed Data (Data Amplification)

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Oct 3, 2026, 3:52 PM
Reserved
Jul 23, 2026, 9:34 PM
Status
Deferred
Published
Oct 2, 2026, 1:17 PM
Modified
Oct 3, 2026, 4:16 PM
Severity
Important
Public date
Oct 2, 2026, 12:58 PM