← Back
CVE-2026-52736
Vulnerability in zebra-state (CVE-2026-52736)
Summary
vulnerability in zebra-state (CVE-2026-52736). Risk of unauthorized operations or information disclosure. Exploitable via ``zebrad``. Mitigation: upgrade to `7.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-52736** has been found in zebra-state.
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 zebra-state to **7.0.0** or later.
If unsure, ask your IT team or search "zebra-state CVE-2026-52736" on the vendor's site.
CVE-2026-52736 (zebra-state) — CWE-459 /
Attack surface: `zebrad` / `network.listen_addr` / `non_finalized_block_write_sent_hashes` / `txid_v5`
Patched: `7.0.0` — apply immediately
Workaround: There is no complete 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-459) exists in zebra-state. Attackers reach the vulnerable code path via ``zebrad`` without authentication.
📍 Affected scope
zebra-state — . Attack surface: `zebrad` / `network.listen_addr` / `non_finalized_block_write_sent_hashes` / `txid_v5`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.0.0**.
🛡️ Workaround
Workaround: There is no complete configuration-level workaround.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'zebra-state' .` 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 'zebra-state' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `zebra-state` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is no complete configuration-level workaround.パッチが適用されるまでの応急処置として、There is no complete configuration-level workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade zebra-state to 7.0.0ステージング環境で 7.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
zebra-state
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0"}]}]
rust
zebrad
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.0"}]}]
References
- web https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-4m69-67m6-prqp
- web https://github.com/ZcashFoundation/zebra/blob/d4cd662c716382f6397d2a730148025a1ca79fec/zebra-state/src/service.rs#L659-L714
- web https://github.com/ZcashFoundation/zebra/blob/d4cd662c716382f6397d2a730148025a1ca79fec/zebra-state/src/service.rs#L797-L802
- web https://github.com/advisories/GHSA-4m69-67m6-prqp