PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-52732 ZcashFoundation CVE debrief

A vulnerability in ZEBRA, a Zcash node written in Rust, allows an unauthenticated P2P peer to monopolize all 25 MAX_INBOUND_CONCURRENCY slots in Zebra's inbound mempool download and verification pipeline. This issue is fixed in version 4.5.0. The vulnerability allows an attacker to advertise fake transaction identifiers and remain silent, causing honest peer transactions and local sendrawtransaction requests to be rejected with MempoolError::FullQueue. Defenders should assess exposure and prioritize upgrading to 4.5.0 if necessary.

Vendor
ZcashFoundation
Product
zebra
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-18
Original CVE updated
2026-09-09
Advisory published
2026-08-18
Advisory updated
2026-09-09

Who should care

Defenders responsible for ZEBRA nodes and Zcash networks should assess exposure and prioritize upgrading to 4.5.0 if necessary. They should also review mempool download and verification pipeline configuration and monitor for suspicious P2P activity. Security teams and vulnerability management teams should track exceptions, retest remediated assets, and close the item only after evidence is documented.

Why it matters

Defenders should prioritize verifying their ZEBRA version and upgrading to 4.5.0 if necessary to prevent potential denial of service and rejected transactions.

  • Potential denial of service due to monopolized mempool download and verification pipeline
  • Rejected honest peer transactions and local sendrawtransaction requests with MempoolError::FullQueue

Technical summary

The vulnerability allows an unauthenticated P2P peer to monopolize all 25 MAX_INBOUND_CONCURRENCY slots in Zebra's inbound mempool download and verification pipeline. An attacker can advertise fake transaction identifiers and remain silent, causing honest peer transactions and local sendrawtransaction requests to be rejected with MempoolError::FullQueue. This issue is fixed in version 4.5.0. Defenders should prioritize verifying their ZEBRA version and upgrading to 4.5.0 if necessary to prevent potential denial of service and rejected transactions.

Defensive priority

Defenders should prioritize verifying their ZEBRA version and upgrading to 4.5.0 if necessary.

Recommended defensive actions

  • Verify ZEBRA version and upgrade to 4.5.0 if necessary
  • Monitor for suspicious P2P activity
  • Review mempool download and verification pipeline configuration
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The vulnerability is described in the CVE record and source references provided. There is limited evidence available from the source corpus. Defenders should verify their ZEBRA version and review mempool download and verification pipeline configuration. The CVE record was published on 2026-08-18T20:17:16.710Z and has not been modified since then. Source references include CVE Program and NIST NVD detail pages.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-52732 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-52732

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-52732 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-52732

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.