← Back
CVE-2026-52734
Vulnerability in zebrad (CVE-2026-52734)
Summary
vulnerability in zebrad (CVE-2026-52734). Risk of unauthorized operations or information disclosure. Exploitable via ``zebrad``. Mitigation: upgrade to `4.5.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-52734** has been found in zebrad.
Attackers can target a specific entry point like ``zebrad`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade zebrad to **4.5.0** or later.
If unsure, ask your IT team or search "zebrad CVE-2026-52734" on the vendor's site.
CVE-2026-52734 (zebrad) — CWE-401 /
Attack surface: `zebrad` / `network.listen_addr` / `cancel_handles` / `RATE_LIMIT_DELAY`
Patched: `4.5.0` — apply immediately
Workaround: There is no configuration-level workaround.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-401) exists in zebrad. Attackers reach the vulnerable code path via ``zebrad`` without authentication.
📍 Affected scope
zebrad — . Attack surface: `zebrad` / `network.listen_addr` / `cancel_handles` / `RATE_LIMIT_DELAY`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.5.0**.
🛡️ Workaround
Workaround: There is no configuration-level workaround.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'zebrad' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'zebrad' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `zebrad` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is no configuration-level workaround.パッチが適用されるまでの応急処置として、There is no configuration-level workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade zebrad to 4.5.0ステージング環境で 4.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
zebrad
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.0"}]}]
References
- web https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-65jj-fmw8-468q
- web https://github.com/ZcashFoundation/zebra/blob/d4cd662c716382f6397d2a730148025a1ca79fec/zebrad/src/components/mempool.rs#L663-L672
- web https://github.com/ZcashFoundation/zebra/blob/d4cd662c716382f6397d2a730148025a1ca79fec/zebrad/src/components/mempool/downloads.rs#L215-L228
- web https://github.com/advisories/GHSA-65jj-fmw8-468q