dbcve.org
ThriftApplication · Apache

CVE-2026-43869

HIGH · 7.3 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 0.23.0 or later.
See remediation →
82/100
Remediation priority · High
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
Improper Validation of Certificate with Host Mismatch 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 · high confidence

Apache Thrift before version 0.23.0 contains an improper certificate validation vulnerability where the library fails to properly validate that the TLS/SSL certificate's host name matches the intended target host. This allows attackers performing man-in-the-middle attacks to intercept encrypted communications by presenting a valid certificate for a different host.

MitigationUpgrade Apache Thrift to version 0.23.0 or later to resolve the certificate host mismatch validation issue.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 version
    Run 'thrift --version' or check your project's dependency management system (Maven, pip, npm, etc.) for the installed Thrift library version
    Affected if The installed version is below 0.23.0 (any version 0.x.y where x < 23, or any version < 0.23.0)
  2. Determine if SSL/TLS transport is in use
    Review your Thrift configuration files and application code for the use of TSocketSSL, TSSLSocket, or any SSL/TLS-enabled transport layer
    Affected if SSL/TLS transport is enabled and the Thrift version is below 0.23.0
  3. Verify client/server TLS certificate validation settings
    Inspect your Thrift client or server initialization code for SSLContext setup, particularly checking whether hostname verification or certificate validation is configured
    Affected if Host mismatch validation is not explicitly enforced and the Thrift version is below 0.23.0

You are affected if Apache Thrift version is below 0.23.0 AND SSL/TLS transport is actively used for client or server communications.

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 certificate host mismatch validation issue.

Recommended fix High confidence

0.23.0

  1. Identify all deployments and applications using Apache Thrift versions prior to 0.23.0
  2. Download Apache Thrift version 0.23.0 from the official Apache Thrift distribution (thrift.apache.org) or trusted package repositories
  3. Replace the existing Thrift library binaries or dependencies with version 0.23.0
  4. Rebuild and recompile any applications that link against the Thrift library
  5. Verify that TLS/SSL certificate validation now properly checks for hostname mismatches (CWE-297 fix)
  6. Deploy the updated applications to production environments
Caveat Review Thrift 0.23.0 release notes for any API or behavioral changes that may affect existing applications

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

Fix this in Thrift Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-43869 — 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-43869 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