Skip to content
major vulnerability· requires attention

Apache Thrift is a widely used backend RPC library; this high-severity RCE can disrupt services and is relevant across many tech stacks.

Applications

CVE-2026-91135

9.2
Critical
EPSS n/aPatch availableOct 2, 2026

Heap overflow in Apache Thrift C++ enabling remote code execution via crafted compressed frames

common questions

Is CVE-2026-91135 being exploited?

Not confirmed. CVE-2026-91135 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.

How severe is CVE-2026-91135?

CVE-2026-91135 is rated Critical with a CVSS score of 9.2. 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-91135?

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

What does CVE-2026-91135 affect?

CVE-2026-91135 affects Apache Thrift (C++) < 0.25.0, Applications using THeaderTransport with ZLIB transform. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-91135?

Upgrade Thrift C++ to >=0.25.0 immediately; block untrusted Thrift traffic

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

executive summary
technical analysis
affected
Apache Thrift (C++) < 0.25.0Applications using THeaderTransport with ZLIB transform
impact

Remote code execution or denial of service via malicious ZLIB-compressed Thrift frames causing heap OOB read/write

action required

Immediate action required

affected versions
Apache Software Foundation Apache Thrift
  • affected< 0.25.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