ThriftApplication · Apache
CVE-2026-41604
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 · uneditedOut-of-bounds Read 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 confidenceOut-of-bounds Read vulnerability in Apache Thrift library affecting versions prior to 0.23.0. This memory safety issue allows reading memory outside allocated buffer boundaries, potentially leading to information disclosure or crash conditions.
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
< 0.23.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate Thrift library installationSearch for Thrift libraries or executables using 'find / -name "*thrift*" -type f 2>/dev/null' on Linux or check common installation paths like /usr/lib/, /usr/local/lib/, or via package manager 'dpkg -l | grep thrift' or 'rpm -qa | grep thrift'Affected if Thrift libraries or executables are found on the system
-
Identify Thrift versionRun 'thrift -version' or check version metadata in installed library files (e.g., 'strings libthrift.so | grep -i version' or examine Thrift's VERSION file if present)Affected if Version output is not available or shows a version string
-
Compare against vulnerable rangeParse the identified version number and compare to 0.23.0 - note that versions like 0.22.0, 0.21.0, 0.20.0, etc. are all < 0.23.0 and thus affectedAffected if Installed version is any release prior to 0.23.0 (e.g., 0.22.x, 0.21.x, older)
The environment is affected if Apache Thrift is installed and the installed version is any release earlier than 0.23.0.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.23.0
Upgrade Apache Thrift to version 0.23.0 or later to resolve the vulnerability.
0.23.0
- Back up your current Thrift installation, configuration files, and any generated code
- Download Apache Thrift version 0.23.0 from the official Apache distribution site (https://thrift.apache.org/)
- Stop any services or applications currently using the existing Thrift version
- Install or deploy Thrift 0.23.0 following the standard installation procedure for your platform
- Verify the installation by running 'thrift --version' to confirm version 0.23.0 is installed
- Regenerate any Thrift IDL files if needed for your applications
- Restart services and test that Thrift-based applications function correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Thrift
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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