RUSTSEC-2026-0428

    Dashboard / Vulnerabilities / RUSTSEC-2026-0428

    RUSTSEC-2026-0428

    Published: 30 Oct 2026Last Modified: 30 Oct 2026

    Summary: BLAKE2b produces wrong tag when using `reset()` with a different-length key

    Details: ## Summary `hazardous::mac::blake2b::Blake2b::reset()` does not correctly reset the state when a key is supplied that has a different length than the one used upon initialization with `hazardous::mac::blake2b::Blake2b::new()`, because it errorneously uses a cached length. ## Impact Initialization `hazardous::mac::blake2b::Blake2b` with a key of some length `N`, followed by a reset with a key of length `!= N` will produce an incorrect BLAKE2b tag, causing `hazardous::mac::blake2b::Blake2b::verify()` to fail. This means under honest protocol conditions, parties could experience failing tag verifications. ## Resolution Upgrade to `v0.17.16` or `v0.18.1`.

    References: https://crates.io/crates/orion, https://rustsec.org/advisories/RUSTSEC-2026-0428.html, https://github.com/orion-rs/orion/pull/690

    Affected packages

    Package

    Name: orion

    Purl: pkg:cargo/orion

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.0.0-0
    Fixed -0.17.16

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    RUSTSEC-2026-0428 | CVE-DB