Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-52739 medium CVSS 5.9

Vulnerability in zebra-state (CVE-2026-52739)

Summary

Vulnerability in zebra-state (CVE-2026-52739). Risk of unauthorized operations or information disclosure. Exploitable via zebrad. Mitigation: upgrade to 7.0.0 or later.

Original description

The description as published by the source.

Am I affected

You are affected if:

  1. You run zebrad up to and including v4.4.1.
  2. Your node processes blocks past the checkpoint height (non-finalized state is active).
  3. The network has NU5 or later activated.

All default configurations are affected.

Summary

Chain::push in the non-finalized state updates the transaction-location index (tx_loc_by_hash) before it runs the duplicate shielded-nullifier guard. When an invalid child block repeats a shielded transaction from its non-finalized parent, the assert_eq!(prior_pair, None, "transactions must be unique within a single chain") fires before the contextual validation that would cleanly reject the duplicate. Under Zebra's panic = "abort" release profile, this terminates the entire node process.

The block should be rejected with a duplicate-nullifier contextual validation error. Instead, the ordering of index updates within Chain::push causes the process to abort.

Details

In zebra-state/src/service/non_finalized_state/chain.rs:1608-1628, the block push sequence is:

  1. Insert transaction hash into tx_loc_by_hash with assert_eq! on uniqueness
  2. Update transparent outputs and inputs
  3. Update shielded data (JoinSplit, Sapling, Orchard) — including nullifier uniqueness checks

The shielded nullifier uniqueness check at step 3 would correctly reject the duplicate transaction. But the assert_eq! at step 1 fires first because the transaction hash is already in tx_loc_by_hash from the pa…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-52739 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: 5.9/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-52739" on the vendor's site.

CVE-2026-52739 (zebra-state) — CWE-248 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: zebrad / tx_loc_by_hash / Entry
Patched: 7.0.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-248) exists in zebra-state. Attackers reach the vulnerable code path via zebrad without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of zebra-state. Attack surface: zebrad / tx_loc_by_hash / Entry.

🔥 Severity

Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.0.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 'zebra-state' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'zebra-state' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で zebra-state を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There is no configuration-level workaround.

    パッチが適用されるまでの応急処置として、There is no configuration-level workaround. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade zebra-state to 7.0.0

    ステージング環境で 7.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]
crates.io zebra-state
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.0.0"}]}]
crates.io zebrad
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.5.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details