SHA-1 Already broken 1 place See details
Hash function in use
`createHash()` or `subtle.digest()`. The digest is read from the argument, so one rule covers the family: MD5 and SHA-1 are reported as broken, SHA-256 as a reduced margin, SHA-384 and above as inventory.
This is already unsafe today, with no quantum computer involved. SHAttered and subsequent work produced practical collisions; NIST withdrew SHA-1 in 2030 guidance and it is already unacceptable for signatures.
What to do. SHA-256 as the floor, SHA-384 where the digest protects something long-lived.
-
packages/ee/server-only/signing/csc/pdf-names.ts:15
const hashToOpaqueSerial = (label: string): string => bytesToHex(sha1(utf8ToBytes(label))).toUpperCase();