Vulnerability BI — sidebar hides with the toggle
Sign in

Weakness Lineage (CWE)

Which weakness classes appear most often in the records in scope, with records carrying no CWE mapping reported rather than dropped.

Mode: Global CVE catalogue
0 CVEs in scope
Global CVE catalogue
Supports investigation
Investigate if present — not detected exposure.

Public CVE records only. Nothing here is evidence that the vulnerability exists on your assets.

Data sources, exact rule, and what is unknown

Powered by: public.cves.cwes via fetchCves · public.canonical_findings in environment mode

Rule: Danger score per CWE = mean CVSS of the records carrying that CWE × ln(count + 1). Records with no CWE mapping are counted separately and reported, never silently dropped.

Not known by this lens:
  • A CWE appearing here does not mean any asset is affected.
  • Records with missing CWE mappings are excluded from CWE rankings and shown as a separate count.

Distinct CWEs

0

Most frequent CWE

Not assessed
0 records

Broadest CWE (vendors)

0
Distinct vendors affected

Records with no CWE mapping

0
Excluded from the ranking; mean 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.

Records with no usable CWE mapping are excluded from the ranking and counted separately in the KPI row; they are never silently dropped.

A CWE appearing here does not mean any of your assets are affected: presence on an asset is not assessed on this lens.

New to CWEs? Read CWE vs CVE explained for how weakness categories relate to individual vulnerabilities.