dbcve.org
ThriftApplication · Apache

CVE-2026-43868

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 0.23.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Memory Allocation with Excessive Size Value vulnerability in Apache Thrift. This issue affects Apache Thrift: before 0.23.0. Users are recommended to upgrade to version 0.23.0, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Memory Allocation with Excessive Size Value vulnerability in Apache Thrift allows an attacker to potentially cause excessive memory allocation, likely through crafted requests that specify unusually large size values, leading to denial of service or resource exhaustion. This affects all versions of Apache Thrift before 0.23.0.

MitigationUpgrade Apache Thrift to version 0.23.0 or later to resolve the vulnerability. Organizations should audit their deployments to identify all instances of the vulnerable library.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ThriftApplication
Affected:< 0.23.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Thrift installation
    Locate Thrift binaries, libraries, or language-specific packages in your environment. Check for thrift compiler executables, libthrift libraries, or Thrift bindings in application dependencies.
    Affected if Apache Thrift is present in the environment
  2. Determine installed Thrift version
    Run 'thrift -version' for the CLI compiler, or check the library version via package managers (pip list, maven, npm, gem, etc.) depending on your language binding.
    Affected if The version cannot be determined or is below 0.23.0
  3. Compare version against affected range
    Review the version number obtained. Apache Thrift versions follow semantic versioning. Check if the major version is 0 and the minor version is less than 23, or if the major version is 0.22.x or earlier.
    Affected if Installed version is less than 0.23.0 (e.g., 0.22.0, 0.21.0, 0.20.0, etc.)
  4. Assess Thrift exposure
    Identify applications or services that use Thrift for network communication. Check if Thrift server endpoints are accessible to network clients or if Thrift-serialized data is processed from untrusted sources.
    Affected if Thrift is actively used to process requests from network clients or untrusted data sources

If the installed Apache Thrift version is 0.22.x or earlier (less than 0.23.0) and the service processes external input, the environment is vulnerable to this memory allocation flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.23.0 or later
Fixed in 0.23.0
Interim mitigation

Upgrade Apache Thrift to version 0.23.0 or later to resolve the vulnerability. Organizations should audit their deployments to identify all instances of the vulnerable library.

Recommended fix High confidence

0.23.0

  1. Identify the current Apache Thrift version in use by running `thrift --version` or checking your project dependencies
  2. Back up all Thrift configuration files, generated code, and any custom modifications
  3. Download Apache Thrift version 0.23.0 from the official Apache Thrift release page (https://thrift.apache.org/download/)
  4. Install the new version following the standard build process for your platform (https://thrift.apache.org/docs/install/)
  5. Verify the upgrade was successful by running `thrift --version` and confirming it shows 0.23.0
  6. Regenerate Thrift bindings for any client applications if necessary and redeploy

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thrift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-43868 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data