CWE-3273 advisories

Use of a Broken or Risky Cryptographic Algorithm

What it is

Weak or misused cryptography (MD5/SHA-1, ECB, static IVs) fails to protect data.

How to fix it

Upgrade and migrate to a modern algorithm/mode with proper key management.

How to avoid it

Use vetted high-level crypto libraries and current algorithms; never roll your own.

Known Use of a Broken or Risky Cryptographic Algorithm vulnerabilities

CVE-2026-54147 — medium · Maven/org.http4k:http4k-security-digest
GHSA-9h47-pqcx-hjr4 — high · npm/better-auth
GHSA-fwg2-gr34-q3w8 — medium · crates.io/surrealdb

Stateward flags Use of a Broken or Risky Cryptographic Algorithm in your own code and dependencies on every pull request.

Scan my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.