# CVE Exploit Priority Monitor – EPSS & Optional CVSS — workflow

## Choose this tool

MSPs, security operations and patch-ticket automation teams enriching CVE IDs they already know.

Useful output columns: `title`, `cveId`, `epssProbability`, `epssPercentile`, `epssDate`, `epssProbabilityChange`, `nvdStatus`, `vulnStatus`, `preferredCvssScore`.

## Practical workflow

Paste a small CVE list from existing tickets or scanner output. Filter current FIRST EPSS scores, keeping probability, percentile and scoring date distinct. Repeat the same snapshot to route confirmed changes; enable NVD details only when additional severity context is needed.

## Check the fit

No asset scanning, affected-asset detection, exploit code or remediation guarantee. Default FIRST-only observations do not verify rejected status, descriptions or CVSS; those fields are null. Optional NVD enrichment has conservative no-key pacing and can be partial during NVD outages. Requested enrichment failures never silently become success. FIRST lookup is for small batches, not a mirror of its full daily dataset. Missing scores produce no FIRST-only row. EPSS model changes can shift scores; dates and probabilities remain explicit.

## Real output sample

One selected row from a 2026-11-16 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: 6I8HGiqEYOcxmOrdL. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "cve:CVE-2021-44228",
  "title": "CVE-2021-44228 · EPSS observation",
  "cveId": "CVE-2021-44228",
  "epssProbability": 0.99999,
  "epssPercentile": 1,
  "epssDate": "2026-11-15",
  "epssProbabilityChange": null,
  "nvdStatus": "not_requested",
  "vulnStatus": null,
  "preferredCvssScore": null,
  "preferredCvssVersion": null,
  "preferredCvssSource": null,
  "lastModifiedAt": null,
  "comparisonStatus": "not_requested"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [CISA KEV Watchlist Monitor - Catalog Changes and EPSS](https://mayd-it.com/data-tools/actors/cisa-kev-watchlist-monitor/)

Check whether CVEs in your EPSS watchlist also appear in CISA’s Known Exploited Vulnerabilities catalog.

1. Take the exact CVE identifiers from cveId and place a small selection in the companion input’s cveIds array.
2. Keep EPSS probability and scoring date separate from CISA inclusion, added date and required-action information.

Source fields: `cveId`. Destination input: `cveIds`.

EPSS estimates probability; KEV records known exploitation under CISA’s criteria. Absence from KEV is not proof of safety, and neither source establishes whether your asset is affected.

### [OSV Package Advisory Monitor](https://mayd-it.com/data-tools/actors/osv-package-advisory-monitor/)

Connect a CVE review with advisories for the exact package versions in your own software inventory.

1. Supply verified ecosystem, package name and version values to the OSV Actor’s packages input. A CVE ID alone is not a package identifier.
2. Review advisory aliases and affected-version evidence before associating a package finding with a CVE watchlist row.

This is a manual identity review, not an automatic CVE-to-package or asset-exposure mapping. Preserve each advisory’s source and affected-version semantics.
