.hero Opens in a new tab
CVE Watch

Every new CVE, filtered to your stack

Search every CVE, build views around the technologies you run, and see exploit, patch and CISA KEV status at a glance.

Problem

A firehose of CVEs, none of them sorted for you

Public feeds publish every CVE for every product. Working out which ones matter is left to your team, and the same three problems keep showing up.

  1. 1
    Too many to readMore than 40,000 CVEs were published in 2024, over 100 a day.
  2. 2
    Which ones are yours?Most hit software you don't run. Finding the one that hits yours means checking each against your stack, by hand.
  3. 3
    How urgent?A severity score alone doesn't say whether an exploit exists, a patch is out, or attackers are already using it.
How we solve it

One feed, shaped around what you run

A view built from your stack

Include the vendors and products you run, exclude the noise, and preview the result before you save. The view keeps watching as new CVEs are published.

Shared with the people who act on it

Add users and teams to a view, give each one a permission level, and let each member choose whether to be notified. The people who fix a CVE hear about it without watching the feed.

Every CVE, explained on one page

Severity with the full CVSS breakdown, exploit, patch, CISA KEV and EPSS, affected versions, weakness type and references. When a CVE applies to you, create a vulnerability from it in one click and it joins your findings.

Key features

Every CVE, in context

Search every CVE

Find any CVE by ID or description, then filter by vendor, product, severity, exploit, patch and dates.

Include and exclude

Conditions in a group must all match, groups combine with OR, and exclusions remove the noise.

Linked to your assets

Link a view to your assets so it follows the technologies they run.

Exploit, patch and KEV

Every CVE shows whether an exploit is known, whether a patch exists, and whether CISA lists it as exploited.

Preview before you save

See exactly which CVEs a view returns while you build it.

Notifications per member

Each member of a view chooses whether to be notified, so the people who act on a CVE hear about it.

How it works

From the whole feed to your feed

  1. 1CVE Search

    Search every CVE

    Look up any CVE by ID or description, and filter by vendor, product, severity, exploit, patch or date.

  2. 2Filters

    Build a view

    Include what you run, exclude what you don't. Link your assets to cover their technologies.

  3. 3Preview

    Preview, then save

    See exactly which CVEs the view returns before you save it.

  4. 4Members

    Share it

    Add users and teams, set each one's permission, and choose who gets notified.

FAQ

Everything you need to know

What is a CVE?

CVE stands for Common Vulnerabilities and Exposures. Each CVE is a public identifier for one disclosed security flaw, like CVE-2024-6387, with a description, the products it affects and a severity score. It gives everyone the same name for the same flaw.

What is CVE monitoring?

Tracking newly published CVEs against the technologies you run, so you hear about the ones that affect you without reading the whole feed. In Panopsys, that's what a CVE view does.

What is the CISA KEV catalog?

The Known Exploited Vulnerabilities catalog, maintained by the US Cybersecurity and Infrastructure Security Agency (CISA). It lists CVEs with evidence of active exploitation. A CVE marked Listed is being used by attackers, so it belongs at the top of your list.

What is an EPSS score?

The Exploit Prediction Scoring System, published by FIRST, estimates the probability that a CVE will be exploited in the next 30 days. Where CVSS says how bad a flaw would be, EPSS says how likely it is to be used. CVE-2024-6387, for example, has an EPSS above 99%.

What do "Potential exploit" and "Patch available" mean?

Potential exploit shows whether exploit code or a known way to exploit the CVE exists. Patch available shows whether a fix has been published. Together with the CISA KEV listing, they tell you how urgent a CVE is, which a severity score alone can't.

How do filters work in a CVE view?

Filters are grouped. Within a group, a CVE must match every condition. Groups are combined with OR, so a CVE that matches any group is included. Exclusion filters then remove every CVE that matches them.

Can I share a CVE view with my team?

Yes. Add users and teams to a view, give each one a permission level, and let each member choose whether to be notified about it.

How is CVE Watch different from a vulnerability scanner?

A scanner checks your machines for known flaws when it runs. CVE Watch follows new CVEs for the technologies you run as they're published, so you can act on a threat to your stack without waiting for the next scan.