FlexTree

Symmetric · Hash-based · niccs.org.cn(opens in a new tab)

Programmes
NGCC R1
Latest version
Round 1 ·
Security flags
Broken (all sets)

Third-party findings: full report on ngcc.dev(opens in a new tab).

Parameter sets

Round 1 · 20 Sep 2026

Parameter sets of FlexTree
Parameter setLevelpk (B)sig (B)pk+sig (B)SignVerify
Flextree-160s Broken128-bit409,5809,6202.31 s6.03 ms
Flextree-160f Broken128-bit4018,67218,712153.26 ms4.37 ms
Flextree-256s Broken256-bit6425,42025,4842.56 s11.04 ms
Flextree-256f Broken256-bit6446,85646,920269.36 ms7.14 ms
Flextree-384s Broken384-bit9660,18060,27612.36 s15.29 ms
Flextree-384f Broken384-bit9673,39673,4923.46 s35.49 ms
Flextree-512s Broken512-bit12894,94895,07623.82 s33.25 ms
Flextree-512f Broken512-bit128117,296117,4246.98 s44.68 ms

Wall-clock times vary between runs and machines (CPU frequency scaling, other tenants on cloud VMs); cycle counts are the steadier basis for comparison.

Security flags

  • Broken (Flextree-160s, Flextree-160f): Verifiers that follow the specification omit its encoding checks and accept forgeries after about 2^40 work. The submitted verifier is not affected (Kudinov).
  • Broken (Flextree-256s, Flextree-256f, Flextree-384s, Flextree-384f, Flextree-512s, Flextree-512f): Grinding a signing counter cuts forgery cost by 20 to 30 bits, below this set's target (Kudinov). Verifiers that follow the specification also accept forgeries after about 2^40 work (Kudinov).

Only one version of FlexTree is recorded, so there is nothing to compare yet.

History

  1. Update

    NGCC round 1: we checked every confirmed critical and high-severity finding on ngcc.dev against our data, and the PKC Forum, the ngcc-harness issues, the public analysis repositories and ePrint for findings ngcc.dev does not list. New broken flags: OPS-DSA, whose specified challenge sampler allows forgery from the public key in 2^39 to 2^90 trials (Xiong and Wang); the compact SQIsign2D2 sets, where one signature yields forgeries on fresh messages (Feussner); BAG-Piglet, whose specified rejection key gives key recovery from decapsulation queries (Saarinen); MAMBA-Viper-384 and -512, whose specification derives every session secret from a 256-bit seed (Saarinen); FlexTree-160, where verifiers that follow the specification accept forgeries after about 2^40 work (Kudinov); TRINE-128, whose specified unsalted round seeds allow forgery in about 2^95 work (Feussner); and UVW-256 signatures, which leak an equivalent signing key as at UVW-128 (Feussner, extended by Saarinen). New warnings: HEP-QC, whose public key is distinguishable from random (Xie), and Rhyme-SHAKE-128, where a signer that follows the specified rejection bound leaks its secret (Feussner). New implementation notes cover rejection keys over the re-encryption (CheetahKEM, LoongKEM), partial FO checks (QUBE), buffer overflows (Amoeba, MORNING-ATLAS), 32-bit message lengths (Aigis-Sig+, CS), message compression and short prehashes (COMPASS-SIG, VDOO, Amoeba), wrapper boundaries and signed-message opening (VDOO, MORNING-ATLAS), malleable encodings (SQIsignTriangle) and fail-open key generation (ZEN). Each flag credits and links its finding.

  2. New version

    Round 1

Full timeline →