ThriftApplication · Apache
CVE-2026-43870
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 · uneditedOrigin Validation Error, Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'), Uncontrolled Resource Consumption 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 confidenceMultiple security vulnerabilities in Apache Thrift before 0.23.0 include path traversal (improper path limitation), HTTP request/response splitting (CRLF injection in headers), origin validation error, and uncontrolled resource consumption. These issues could allow attackers to access restricted directories, inject HTTP headers, or cause denial of service.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Thrift installed versionRun 'thrift --version' or check your package manager (e.g., pip show thrift, maven dependency tree, npm list thrift) for the installed Thrift library versionAffected if The installed version is below 0.23.0 (e.g., 0.22.0, 0.21.0, 0.20.0, etc.)
-
Check if HTTP server component is in useInspect your application code and runtime configuration for imports and usage of THttpServer, TServlet, or any HTTP-based Thrift service endpointsAffected if Your application serves Thrift over HTTP/HTTPS endpoints using the built-in HTTP transport/server modules
-
Verify path handling in file transfer featuresSearch your codebase for TFileTransport, TFDTransport, or any custom file transfer implementations that handle file paths provided by clientsAffected if Your Thrift service accepts file paths from clients and uses them in server-side file operations without strict validation
-
Inspect HTTP header processingReview code that sets custom HTTP headers in responses, particularly looking for header values derived from user input or未经 sanitized dataAffected if Your application uses Thrift's HTTP transport and sets response headers with values that could be influenced by client input
-
Check for origin validation in CORS or cross-origin requestsSearch for origin checking logic in your Thrift HTTP server implementation (look for 'origin', 'Access-Control-Allow-Origin', or similar header handling)Affected if Your Thrift HTTP server implements CORS or origin validation logic for cross-origin requests
You are affected if Apache Thrift version is below 0.23.0 AND your application uses the HTTP server component, accepts file paths from clients, processes custom HTTP headers, or implements cross-origin request handling.
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 all reported vulnerabilities.
Apache Thrift 0.23.0
- 1. Identify your current Apache Thrift version by running `thrift --version` or checking your dependency management system
- 2. Back up your current Thrift installation and any configuration files
- 3. Download Apache Thrift version 0.23.0 from the official Apache Thrift releases repository (https://thrift.apache.org/download/)
- 4. Install the new version following the official installation guide for your operating system (https://thrift.apache.org/docs/install/)
- 5. Verify the upgrade was successful by running `thrift --version` and confirming it shows 0.23.0
- 6. Test your applications and services that depend on Thrift to ensure functionality is intact
- 7. Review the release notes for 0.23.0 to check for any migration requirements or deprecation notices
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Thrift
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43870 — 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-43870 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