I built a live vulnerability intelligence dashboard that tracks trending CVEs, severity levels, and basic exploitation signals.
The goal was to make CVE data easier to scan quickly without digging through multiple feeds.
You can view it here: https://leakycreds.com/vulnerability-intelligence
Each CVE has its own page with:
* Overview and description * CVSS score and severity * Impact summary * References * Last updated timestamp * Linked social media posts related to that CVE (to understand why it’s trending)
It’s free to access — no login required to browse vulnerability data.
I’m currently refining:
* How trending CVEs are prioritized * How to surface exploitation signals more clearly * What contextual signals are actually useful during triage
Would really appreciate feedback:
* What do you look at first when triaging a new CVE? * What do most vulnerability dashboards get wrong? * What would make something like this genuinely useful for your workflow?
Happy to answer technical questions as well.
saynsec•1h ago