Zebra RpcApplication · Zfnd
CVE-2026-41585
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 · uneditedZEBRA is a Zcash node written entirely in Rust. From zebrad versions 2.2.0 to before 4.3.1 and from zebra-rpc versions 1.0.0-beta.45 to before 6.0.2, a vulnerability in Zebra's JSON-RPC HTTP middleware allows an authenticated RPC client to cause a Zebra node to crash by disconnecting before the request body is fully received. The node treats the failure to read the HTTP request body as an unrecoverable error and aborts the process instead of returning an error response. This issue has been patched in zebrad version 4.3.1 and zebra-rpc version 6.0.2.
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 confidenceA denial-of-service vulnerability in Zebra's JSON-RPC HTTP middleware allows an authenticated RPC client to crash the node by disconnecting before the request body is fully received. The node incorrectly treats the failure to read the HTTP request body as an unrecoverable error and aborts the process instead of gracefully handling the incomplete request and returning an error response.
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
Zebra RpcApplication
>= 2.0.0, < 6.0.2= 1.0.0
ZebradApplication
>= 2.2.0, < 4.3.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Check zebrad versionRun 'zebrad --version' or check the zebrad binary metadataAffected if Version is >= 2.2.0 and < 4.3.1
-
Check zebra-rpc versionInspect the Cargo.lock file or dependency manifest for the zebra-rpc crate version, or check the zebrad build configurationAffected if Version is >= 2.0.0 and < 6.0.2, or version equals 1.0.0
-
Verify JSON-RPC HTTP is enabledInspect zebrad config file (default at ~/.zebrad.toml or /etc/zebrad.toml) for RPC HTTP listener configuration under [rpc] or [rpc.http] sectionAffected if An HTTP RPC listener is configured and active
A user is affected if they run a vulnerable zebrad (2.2.0 to < 4.3.1) or zebra-rpc (1.0.0 or 2.0.0 to < 6.0.2) with the JSON-RPC HTTP interface enabled.
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 · scoped4.3.16.0.2
Upgrade zebrad to version 4.3.1 or later and zebra-rpc to version 6.0.2 or later to receive the patch that properly handles incomplete request bodies as recoverable errors.
zebrad version 4.3.1 or zebra-rpc version 6.0.2
- 1. Identify which Zebra component is affected in your deployment (zebrad node, zebra-rpc library, or both)
- 2. For zebrad: Update to version 4.3.1 or later using your package manager or by rebuilding from source with the updated version tag
- 3. For zebra-rpc: Update to version 6.0.2 or later by updating the dependency in your Cargo.toml file
- 4. After upgrading, verify the node starts successfully and test RPC functionality
- 5. Monitor the node to confirm it no longer crashes when clients disconnect prematurely
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Zebra Rpc
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41585 — 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-41585 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