Is CVE-2026-43868 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-43868 being exploited in the wild.

How severe is CVE-2026-43868?

Medium severity, with a CVSS score of 5.3, published 5 May 2026.

Which products and versions are affected?

thrift (crates.io) SEMVER:introduced=0,fixed=0.23.0, SEMVER:introduced=0.0.0-0,fixed=0.23.0; Red Hat build of Apache Camel for Quarkus 3, 3.33.

Is there a fix for CVE-2026-43868?

Yes. thrift (crates.io): upgrade to 0.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-43868 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-43868?

Check whether you run Apache Thrift, thrift (crates.io) or Red Hat build of Apache Camel for Quarkus 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.

CVE-2026-43868: Apache Thrift denial of service via excessive memory allocation

CVE-2026-43868 · Severity: medium · CVSS 5.3 · Published 2026-05-05

Apache Thrift, a framework for cross-language services development, is vulnerable to a memory allocation issue. An attacker can send a specially crafted request that forces the system to allocate an excessive amount of memory, potentially leading to a denial-of-service condition where the application becomes unresponsive. This impacts the availability of services relying on the Thrift library for communication.

Technologies: Apache Thrift, Red Hat build of Apache Camel for Quarkus. Vendors: Apache, crates.io, Red Hat.

Quick answers

Is CVE-2026-43868 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-43868 being exploited in the wild.
How severe is CVE-2026-43868?: Medium severity, with a CVSS score of 5.3, published 5 May 2026.
Which products and versions are affected?: thrift (crates.io) SEMVER:introduced=0,fixed=0.23.0, SEMVER:introduced=0.0.0-0,fixed=0.23.0; Red Hat build of Apache Camel for Quarkus 3, 3.33.
Is there a fix for CVE-2026-43868?: Yes. thrift (crates.io): upgrade to 0.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-43868 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-43868?: Check whether you run Apache Thrift, thrift (crates.io) or Red Hat build of Apache Camel for Quarkus 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

thrift (crates.io): upgrade to 0.23.0 or later
```
cargo update -p thrift
```

Technical details

Apache Thrift before version 0.23.0 contains a Memory Allocation with Excessive Size Value vulnerability (CWE-789) and improper validation of input offsets (CWE-1285). The vulnerability occurs when the library allocates memory based on an untrusted size value provided in a network request without ensuring the size is within reasonable limits. A remote, unauthenticated attacker can exploit this by sending a malicious payload with a large size value, causing the application to exhaust available memory and crash or hang (Denial of Service). The issue is addressed in version 0.23.0.

Affected products

Apache Thrift < 0.23.0

Identifiers

CVE-2026-43868
BIT-THRIFT-2026-43868
GHSA-2f9f-gq7v-9h6m
RUSTSEC-2026-0435

Timeline

2026-05-05: disclosed
2026-05-05: advisory
2026-05-08: other: GitHub reviewed the advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.