CVE Tools
Sign in
Back to blog
release-notes

Clearer CVE explainers, and a blog with diagrams

CVE Tools··3 min read

Hey there 👋 The last few days were all about making the why clearer — a sharper read on what a CVE actually means, and a proper home for these very updates. Here's what landed.

✨ What's new for you

  • Sharper plain-language explainers. Trending CVEs now get an explainer that reads the advisory in parts and then stitches the findings into one clear write-up — so the what it means is better organised, more accurate, and no longer lists the same vendor twice. Open any trending CVE to see it.
  • The blog has a real home. There's now a Blog link right in the top menu, and the /blog index got a clean, news-style redesign — these release notes live here now, not buried in GitHub.
  • Articles can draw you a picture. A new interactive diagram block lets a post lay out an attack chain or a pipeline as a graph you can actually explore — there's a live one just below. 👇
  • Smarter CVE browsing. We ran a big cleanup over every CVE's affected products and normalised vendor and product names. That powers a new product-family filter when you browse CVEs, plus public vendor and product hubs you can explore by sector — jump straight to what runs on your stack.
  • News that connects the dots. Press coverage now groups by the CVE it's about, so one click takes you from a story to every related article — and back to the CVE itself.
  • Plug cve.tools into your AI assistant. Our MCP server hit a rough patch and was down for a bit — it's now fully fixed and solid again. Connect cve.tools to Claude (or any MCP client) and ask about any CVE in plain language: it pulls live scores, EPSS, KEV status, exploits and fixes for you.

🔀 Here's that new diagram block

This is the new block in action — the path a CVE takes to become a plain-language explainer. It's live, not a screenshot: hover and drag the nodes around.

How a CVE becomes a plain-language explainer

  1. Advisory + CVE data — Everything we know about the flaw
  2. Read it in parts — Each section is analysed on its own
  3. De-dupe affected products — One canonical name per vendor
  4. Synthesize — Stitch the findings into one read
  5. Plain-language explainer — What it means — no jargon

🛠 Smoother now

  • Blog articles picked up breadcrumbs and wider code blocks — easier to follow a long read and copy a command without it wrapping.
  • The scan card that surfaces a CVE's explainer got a cleaner redesign, so the key facts read at a glance.

We'd love your take

Spotted something off, or have an idea you wish we'd build next? Open a bug or drop an idea — we read every one.

_Covers changes shipped between 2026-06-24 and 2026-06-28. Thanks for building alongside us._ 💙