Vulnerability BI — sidebar hides with the toggle
Sign in

Weakness Lineage (CWE)

Understand patterns: group weaknesses into engineering themes so you can fix categories of bugs, not one CVE at a time.

0 CVEs in scope

Distinct CWEs

0

Top CWE

—
0 CVEs

Broadest CWE (vendors)

0
Distinct vendors affected

Avg severity of top 15

0.0
How this works — definitions, thresholds, and what to doShow

Danger score per CWE = average severity × log(frequency). A dangerous cluster is both common and serious.

Engineering themes the top CWEs typically roll up into:

  • AuthN / AuthZ — 287, 306, 863, 862.
  • Memory safety — 119, 787, 416, 125.
  • Injection — 78, 79, 89, 94.
  • Path & deserialisation — 22, 502.
  • Crypto & secrets — 327, 798, 522.

Do next: pick the top theme and open an engineering-wide remediation initiative (linting, SDL rule, framework upgrade) — not a per-CVE ticket.

Help