How we rate
Every page answers three questions:
How scary is it, are you affected, and what should you do.
The scare-o-meter
- ShrugReal, but not worth losing sleep over.
- Keep an eye on itPatch on schedule. Watch for news.
- Check todayFind out if you're affected. If you are, patch.
- Drop everythingAttackers are already on it. Patch now.
What moves the needle, biggest first:
Attacks seen in the wild, a listing on CISA's exploited list, public exploit code, whether it works without logging in, and how common the affected setup is.
A scary CVSS score on its own doesn't move it.
Verdicts
- Patch now
- Working exploit or attacks seen, and common setups are exposed.
- Patch now if…
- Serious, but only under conditions we list. Each page shows you how to check them.
- Next cycle
- Real, but hard to reach or low impact. Patch on your normal schedule.
- Watching
- People are talking about it, but too little is known to act on. We say what would change that, and update the page when it does.
The checklist
- Works without logging in
- The attacker needs no account, password or certificate.
- Public exploit code is out
- Working code anyone can download. A blog post or video doesn't count, and neither do the fake exploits that show up after every big CVE.
- Shown working
- A researcher demonstrated it, but hasn't published the code.
- Attacks seen in the wild
- A credible report from the vendor, CISA or a named security team.
- On CISA's exploited list
- Listed in CISA's Known Exploited Vulnerabilities catalog. The fix-by date is the US federal deadline, which is a good default for everyone else.
House rules
- Every claim has a source. Click the little numbers.
- Every change is logged. Facts move fast in the first days. Each page has a changelog.
- We show you how to check. We never tell you you're safe.
- We skip the noise. We only cover the CVEs people are actually asking about.
- We get things wrong sometimes. Tell us on X (@tldrcve) and we'll fix it, in the open.