CVE-2026-41585: Zebra Vulnerable to Denial of Service via Interrupted JSON-RPC Requests from Authenticated Clients

CVE-2026-41585 · Severity: medium · CVSS 3.1 · Published 2026-04-18

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.

## Severity **Moderate** - This is a Denial of Service (DoS) that requires a client capable of passing Zebra's cookie authentication, which is enabled by default.

## Affected Versions - `zebrad`: versions from **2.2.0** up to (but not including) **4.3.1** - `zebra-rpc`: versions from **1.0.0-beta.45** up to (but not including) **6.0.2**

## Description

Zebra's JSON-RPC HTTP middleware treated a failure to read the incoming HTTP request body as an unrecoverable error, aborting the process rather than returning an error response. A client that disconnected after sending only part of a request body, for example, by resetting the TCP connection mid-transfer, was sufficient to trigger the crash. The vulnerability could be exploited only by authenticated RPC clients. Nodes running the shipped defaults, with RPC bound to localhost and cookie authentication on, were not vulnerable.

## Impact **Denial of Service** * **Attack Vector:** Network, authenticated (requires a valid RPC cookie when cookie authentication is enabled). * **Effect:** Immediate crash of the Zebra node. * **Scope:** Any node whose RPC interface is reachable by a client with valid credentials, or any node with cookie authentication disabled and an exposed RPC interface.

## Fixed Versions This issue is fixed in **Zebra 4.3.1** (crate `zebra-rpc` 6.0.2).

The fix propagates failures to read the HTTP request body as ordinary error responses, so Zebra now rejects truncated or interrupted requests rather than crashing.

## Mitigation Users should upgrade to **Zebra 4.3.1** or later.

If an immediate upgrade is not possible, users should ensure their RPC port is not exposed to untrusted networks and that cookie authentication remains enabled (the default).

## References * [Zebra 4.3.1 Release Announcement](https://zfnd.org/)

## Credits Thanks to [shieldedonly](https://github.com/shieldedonly) who discovered this issue and reported it via our coordinated disclosure process.

Technologies: zebra-rpc (crates.io), zebrad (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2026-41585 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41585 being exploited in the wild.
How severe is CVE-2026-41585?
Medium severity, with a CVSS score of 3.1, published 18 April 2026.
Which products and versions are affected?
zebra-rpc (crates.io) >= 1.0.0-beta.45, < 6.0.2, SEMVER:introduced=1.0.0-beta.45,fixed=6.0.2; zebrad (crates.io) >= 2.2.0, < 4.3.1, SEMVER:introduced=2.2.0,fixed=4.3.1.
Is there a fix for CVE-2026-41585?
Yes. zebra-rpc (crates.io): upgrade to 6.0.2 or later; zebrad (crates.io): upgrade to 4.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-41585?
Check whether you run zebra-rpc (crates.io) or zebrad (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • zebra-rpc (crates.io): upgrade to 6.0.2 or later
    cargo update -p zebra-rpc
  • zebrad (crates.io): upgrade to 4.3.1 or later
    cargo update -p zebrad

Affected products

  • zebra-rpc (crates.io) >= 1.0.0-beta.45, < 6.0.2, SEMVER:introduced=1.0.0-beta.45,fixed=6.0.2
  • zebrad (crates.io) >= 2.2.0, < 4.3.1, SEMVER:introduced=2.2.0,fixed=4.3.1

Identifiers

  • CVE-2026-41585
  • GHSA-29x4-r6jv-ff4w

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.