Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46654

Vulnerability in p3-challenger (CVE-2026-46654)

Summary

Vulnerability in p3-challenger (CVE-2026-46654). Risk of unauthorized operations or information disclosure. Exploitable via transcript_malleability. Mitigation: upgrade to 0.5.3 or later.

Original description

The description as published by the source.

Impact

  • Key: challenger/src/multi_field_challenger.rs | MultiField32Challenger::duplexing | transcript_malleability

  • Affected files: challenger/src/multi_field_challenger.rs, field/src/helpers.rs

  • Violated invariant: The Fiat-Shamir sponge must bind challenges to the exact sequence of observed field elements. Specifically: (1) absorption must be injective — distinct observation streams must produce distinct sponge states, (2) squeezing must be injective — distinct PF rate cells must yield distinct F challenge sequences, and (3) all bits of each absorbed PF element must influence the sponge state.

  • Exploit scenario: An attacker controlling prover-side observations can craft distinct transcripts that produce identical challenges, breaking the binding property of Fiat-Shamir. Three independent attack vectors exist:

    1. Partial-chunk aliasing (absorb): duplexing() packs input_buffer.chunks(num_f_elms) via reduce_32 (base 2^32) with no length marker and no zeroing of unused rate slots. Observing [x] followed by a sample yields the same sponge state as [x, 0, ..., 0] (padded to num_f_elms) followed by a sample, since reduce_32 treats missing high limbs identically to explicit zeros. The attacker can extend or truncate the tail of any observation batch without changing future challenges.

    2. Non-injective squeeze (squeeze): split_32 decomposes each PF rate cell into base-2^64 digits and maps each through TF::from_u64,…

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-46654 has been found in p3-challenger.
Attackers can target a specific entry point like transcript_malleability over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade p3-challenger to 0.5.3 or later.
If unsure, ask your IT team or search "p3-challenger CVE-2026-46654" on the vendor's site.

CVE-2026-46654 (p3-challenger) — CWE-345
Attack surface: transcript_malleability / reduce_32 / num_f_elms / split_32
Patched: 0.5.3 — apply immediately
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-345) exists in p3-challenger. Attackers reach the vulnerable code path via transcript_malleability.

📍 Affected scope

Check the vendor advisory for the affected versions of p3-challenger. Attack surface: transcript_malleability / reduce_32 / num_f_elms / split_32.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.5.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'p3-challenger' . 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 'p3-challenger' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade p3-challenger to 0.5.3

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

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

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

Affected packages

rust p3-challenger
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.3"}]}]
crates.io p3-challenger
[{"type":"SEMVER","events":[{"introduced":"0.5.0"},{"fixed":"0.5.3"}]}]

References

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