CVE & CISA-KEV Catalog

CVE-2026-52734

MEDIUM
5.3
CVSS v3
NVD

Description

ZEBRA is a Zcash node written entirely in Rust. Prior to 4.5.0, an unauthenticated P2P peer can cause the mempool download pipeline to retain transactions after verification reaches the outer RATE_LIMIT_DELAY timeout. In zebrad/src/components/mempool/downloads.rs, Downloads::poll_next removed cancel_handles entries after success and ordinary verification errors, but tokio::time::error::Elapsed did not carry the UnminedTxId needed to remove the timed-out entry. Each retained cancel_handles entry could hold a full Gossip::Tx(UnminedTx), while normal mined-transaction cleanup could not match attacker transactions and no periodic garbage collection or count cap existed. Sustained traffic therefore caused monotonic memory growth until swap pressure degraded the node or the operating system terminated the zebrad process for exhausting memory. This issue is fixed in version 4.5.0.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityLow

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploit Intelligence

0.37%probability of exploitation in 30 days
30thpercentile

Low risk: more likely to be exploited than 30% of all known CVEs.

References

Related Vulnerabilities

Other CWE-401 (Missing Release of Memory (Memory Leak)) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2020-13934High7.564%-Fix
CVE-2016-6304High7.563%-Fix
CVE-2019-12265Medium5.360%-Fix
CVE-2001-0136Medium5.045%--
CVE-2016-4232High7.536%--
CVE-2001-0543Medium5.019%--

Common questions

How do I fix CVE-2026-52734?

No published fix for CVE-2026-52734 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-52734 being actively exploited?

Not that we know of. CVE-2026-52734 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.37% is the estimated probability that it will be exploited in the next 30 days. That is higher than 30% of all scored CVEs.

How severe is CVE-2026-52734?

CVE-2026-52734 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-52734
CVE-2026-52734 severity badge

Markdown

[![CVE-2026-52734](https://tridentstack.com/cve/badge/CVE-2026-52734.svg)](https://tridentstack.com/cve/CVE-2026-52734)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-52734"><img src="https://tridentstack.com/cve/badge/CVE-2026-52734.svg" alt="CVE-2026-52734"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.