An issue exists in the mempool coinbase-maturity check where the system performs quadratic work. This occurs because the `coinbase spend restriction()` function rebuilds the transaction output list for every spent outpoint. A connected peer can exploit this by repeatedly sending unsigned transactions containing numerous transparent inputs and outputs. These transactions are rejected without triggering a misbehavior score, allowing an attacker to pin verification threads.