Loading...
Skip to main content

CVE-2026-41585

MEDIUM

Zebra Vulnerable to Denial of Service via Interrupted JSON-RPC Requests from Authenticated Clients

Published April 18, 2026Updated May 12, 2026Source: osv

Summary

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.

Remediation

Upgrade to the fixed version using your package manager.

Cargo
Update zebra-rpc to 6.0.2 or later
cargo update -p zebra-rpc --precise 6.0.2
Cargo
Update zebrad to 4.3.1 or later
cargo update -p zebrad --precise 4.3.1

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

PackageEcosystemAffectedFixed In
zebra-rpc
crates.io
All versions6.0.2
zebrad
crates.io
All versions4.3.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 6.5 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
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

Frequently Asked Questions

What is CVE-2026-41585?
Zebra Vulnerable to Denial of Service via Interrupted JSON-RPC Requests from Authenticated Clients This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 6.5/10).
How do I check if my project is affected by CVE-2026-41585?
CVE-2026-41585 affects zebra-rpc and zebrad. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-41585 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
6.5

Exploitation requires specific conditions or has limited impact. Remediate within weeks.

Also Known As

GHSA-29x4-r6jv-ff4w

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies