Skip to content
Applications

CVE-2026-43871

8.7
High
EPSS 0.61%Patch availableJul 27, 2026

Infinite-loop DoS in Apache Thrift (<0.24.0) affecting multiple language bindings

common questions

Is CVE-2026-43871 being exploited?

Not confirmed. CVE-2026-43871 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.61% probability of exploitation in the next 30 days.

How severe is CVE-2026-43871?

CVE-2026-43871 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-43871?

Yes. A fix has been recorded for CVE-2026-43871. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-43871 affect?

CVE-2026-43871 affects Apache Thrift < 0.24.0 (Python binding), Apache Thrift < 0.24.0 (Go binding), Apache Thrift < 0.24.0 (PHP binding), Apache Thrift < 0.24.0 (Java binding). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43871?

Upgrade Apache Thrift to 0.24.0 immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Thrift < 0.24.0 (Python binding)Apache Thrift < 0.24.0 (Go binding)Apache Thrift < 0.24.0 (PHP binding)Apache Thrift < 0.24.0 (Java binding)
impact

Crafted Thrift RPC inputs can trigger an infinite loop in Python/Go/PHP/Java bindings, causing CPU hang/service denial of service.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Thrift
  • affected< 0.24.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free