May’d It
CVE Exploit Priority Monitor — illustrative workflow

DATA TOOLS / ai

CVE Exploit Priority Monitor – EPSS & Optional CVSS

Track daily FIRST EPSS probabilities, percentiles and score dates for a CVE watchlist. Save confirmed changes for patch-ticket workflows; optionally enrich with attributed NVD CVSS and descriptions. No API keys or asset scanning.

JSON / CSV outputLimited permissionsSource: maydit/cve-exploit-priority-monitor

FROM SOURCE TO A USEFUL RESULT

A practical workflow

Choose this tool when…

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

titlecveIdepssProbabilityepssPercentileepssDateepssProbabilityChangenvdStatusvulnStatuspreferredCvssScore

Which known CVEs changed in daily exploit probability?

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 and source limits

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.

Download this workflow as Markdown · Configure a small first run

REAL RUN · DATED EVIDENCE

See an actual saved result

Captured 2026-11-16. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.

{
  "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"
}

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health. Run reference: 6I8HGiqEYOcxmOrdL. Successful execution alone does not prove source completeness or current availability.

START SMALL

Example input

Historical evidence for this exact JSON was recorded 2026-11-16 on its original build. This is not a fresh source-availability test. Adjust targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.

{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-34362"
  ],
  "maxResults": 5,
  "includeNvdDetails": false
}
Download input.json

CHOOSE A STARTING POINT

3 ready-to-use inputs

Pick a focused example, copy or download its JSON, then review the inputs and current pricing in your own Apify account. Downloading a configuration does not start a run.

Default input · Input schema · Saved output capture

Prioritize two existing patch tickets

Fetch current FIRST probability, percentile and date for Log4Shell and MOVEit without adding a second source dependency.

{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-34362"
  ],
  "maxResults": 5,
  "includeNvdDetails": false
}

Saved run evidence: 2026-11-16 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Check one CVE’s daily EPSS

Return the scored Log4Shell observation with explicit FIRST source and scoring date; NVD metadata is not requested.

{
  "cveIds": [
    "CVE-2021-44228"
  ],
  "maxResults": 1,
  "includeNvdDetails": false
}

Saved run evidence: 2026-11-16 UTC · 1 saved row. This is a historical check, not live data or a guarantee that every query will succeed today.

Filter a high-probability watchlist

Keep scored CVEs whose EPSS probability is at least 0.5; this is prioritization evidence, not an exposure verdict.

{
  "cveIds": [
    "CVE-2021-44228",
    "CVE-2023-34362"
  ],
  "minimumEpss": 0.5,
  "includeUnscored": false,
  "maxResults": 5,
  "includeNvdDetails": false
}

Saved run evidence: 2026-11-16 UTC · 2 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Download all example inputs and evidence references

A CLEAR DATA CONTRACT

Inputs you can configure

FieldTypeMeaning
cveIdsarray

One to ten exact CVE IDs from your vulnerability inventory. No targets or assets are scanned.

minimumEpssnumber

0–1 probability threshold, not percent. An EPSS score does not establish exposure or severity.

includeUnscoredboolean

Applies only with NVD enrichment: preserve a confirmed NVD CVE when FIRST has no score, using null values. In FIRST-only mode, absent scores never produce placeholder rows.

includeRejectedboolean

Applies only with NVD enrichment. By default NVD-rejected records are filtered. FIRST-only mode does not check CVE rejection status and leaves isRejected null.

maxResultsinteger

A billed result is one confirmed saved observation. Truncation prevents history advancement.

comparePreviousboolean

The first complete run establishes history. Partial/failed/capped runs never advance it.

onlyChangesboolean

Enables comparison. Unchanged runs may save zero rows. Source-date changes can count as changes.

snapshotNamestring

1–80 letters, digits, underscores or hyphens. Inputs/filters/output cap also separate history.

maxRunSecondsinteger

One FIRST batch request by default. Optional NVD requests are paced 6.5 seconds each; shared upstream delays can make large enriched watchlists partial.

includeNvdDetailsboolean

Optional slower enrichment through the public NVD API, paced 6.5 seconds per request. NVD outages produce an explicit partial/failed run, never a silent EPSS-only fallback. The default checks FIRST only.

Output fields

titlecveIdepssProbabilityepssPercentileepssDateepssProbabilityChangenvdStatusvulnStatuspreferredCvssScorepreferredCvssVersionpreferredCvssSourcelastModifiedAtcomparisonStatussourceUrl

These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.

Input schema JSON

KNOW THE COST

Event pricing

Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.

EventUSD per eventWhat is charged
Actor Start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Saved observation$0.003One validated observation confirmed saved to the dataset.

Check current Apify pricing ↗ before running.

Use with an AI agent or API

Connect this Actor through MCP

Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the official configurator provides client-specific instructions.

{
  "mcpServers": {
    "maydit": {
      "url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/cve-exploit-priority-monitor"
    }
  }
}

Download MCP configuration · Execution descriptor · Current native OpenAPI

Ask the agent to inspect maydit/cve-exploit-priority-monitor (Actor ID dpFnSzv8xbPhu181z) with fetch-actor-details, including input, output and pricing. Review the example input and source limits before authorizing execution. For call-actor, place a maximum charge of $0.05 and timeout of 300 seconds in callOptions, not the Actor input. A spending cap can stop a run before its intended scope completes.

After starting once, keep the returned run ID. Use get-actor-run for status, get-key-value-store-record for that run's SUMMARY, and get-dataset-items with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.

Supply your own credentials

For direct API use, set APIFY_TOKEN securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.

This input schema has no source-credential fields. Apify authorization is still required to start a paid run.

Start once, then retrieve the same run

Download run-actor.mjs, execution.json and input.json into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.

# Preview only: makes no requests
node run-actor.mjs

# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run

# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run

The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.

It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.

Review run-status.json, summary.json, items.json and download-receipt.json. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.

For a custom integration, use the same sequence:

  1. POST https://api.apify.com/v2/actors/dpFnSzv8xbPhu181z/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS with a JSON input body and Bearer authorization. Save data.id once.
  2. GET https://api.apify.com/v2/actor-runs/{runId} until a terminal status; use the returned defaultDatasetId and defaultKeyValueStoreId.
  3. GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY; interpret diagnostics using this Actor's coverage guide.
  4. GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100; paginate the same completed dataset and retain source URLs/timestamps.

The official run API, dataset pagination documentation and MCP guide describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.

BUILD A REVIEWED WORKFLOW

Use this with companion tools

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

Manual data handoff

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: 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.

Read the companion guide →

Parallel research context

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.

Read the companion guide →

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Source contract captured from build 1.0.2. Presentation refreshed 2026-11-16. Example outputs retain their original sample context; they are not live results.

CVE Exploit Priority Monitor – EPSS & Optional CVSS

Turn known CVE identifiers into dated exploit-probability observations for patch tickets and security dashboards. Track FIRST EPSS probability, percentile and score changes. Add NVD descriptions and attributed CVSS scores when you need extra severity context.

Built for MSPs, vulnerability-management teams and ticket automations that already have a CVE inventory. This Actor does not scan assets or determine whether a particular system is vulnerable.

Start with a useful result

Paste one to ten CVE IDs. The default makes one small-batch request to FIRST, requires no key or proxy, and saves only actual scored observations. Open the dataset for records, SUMMARY for coverage, and RUN_REPORT for a readable run explanation.

Prioritize two existing patch tickets

Fetch current FIRST probability, percentile and date for Log4Shell and MOVEit without adding a second source dependency.

{
  "cveIds": ["CVE-2021-44228", "CVE-2023-34362"],
  "maxResults": 5,
  "includeNvdDetails": false
}

Check one CVE’s daily EPSS

Return the scored Log4Shell observation with explicit FIRST source and scoring date; NVD metadata is not requested.

{
  "cveIds": ["CVE-2021-44228"],
  "maxResults": 1,
  "includeNvdDetails": false
}

Filter a high-probability watchlist

Keep scored CVEs whose EPSS probability is at least 0.5. This is prioritization evidence, not an exposure verdict.

{
  "cveIds": ["CVE-2021-44228", "CVE-2023-34362"],
  "minimumEpss": 0.5,
  "includeUnscored": false,
  "maxResults": 5,
  "includeNvdDetails": false
}

Read the scores correctly

Field Meaning
epssProbability A 0–1 probability of exploitation in the wild over the next 30 days from the scoring date. It is not a percentage or an asset-specific exposure verdict.
epssPercentile The source percentile, also 0–1. It is separate from the probability.
epssDate FIRST’s scoring date; distinct from this Actor’s observedAt.
epssProbabilityChange Difference from the previous complete observation in the same snapshot.
nvdStatus not_requested for the default mode; available only after a validated NVD response.
sourceUrl The exact official source lookup for this observation.

Every row includes recordId, observedAt, contentHash, comparisonStatus and changedFields. FIRST-only rows leave NVD description, CVSS, rejection status and NVD dates null. They do not claim that the CVE is analyzed, non-rejected or applicable to your systems. An identifier missing from a complete FIRST response is recorded in SUMMARY.unscored and produces no placeholder or billed result.

Optional NVD enrichment

Set includeNvdDetails:true to fetch NVD details for each requested CVE after FIRST succeeds. This slower mode adds the official description, CVE status, publication/modification dates, CWE identifiers, references and all supported CVSS 2.0/3.0/3.1/4.0 scoring sources. Each CVSS score retains its version, source and Primary/Secondary attribution. The preferred score uses the highest version with a Primary score; a unique NVD Primary wins if several exist. Unresolved ambiguity remains null rather than selecting the highest numeric score.

NVD requests are paced at least 6.5 seconds apart, including before the first request. Public NVD availability varies. A requested enrichment failure produces a partial or failed run and preserves history; it never silently becomes an EPSS-only success. Confirmed observations from other CVEs may still appear in a partial dataset.

includeUnscored and includeRejected apply to NVD-enriched records. A confirmed NVD CVE without a FIRST score can retain null EPSS fields when includeUnscored:true. Rejected NVD records are filtered unless explicitly included. A valid NVD “not found” answer creates no result row.

Compare complete checks

Set comparePrevious:true to establish a baseline and compare later runs. onlyChanges:true also enables comparison and skips unchanged observations; a correct repeat can save zero rows. History is separated by watchlist, filters, enrichment mode, snapshotName and result cap. Use a snapshot sequentially; conflicting concurrent writers cannot overwrite its history.

Only complete successful source collection and confirmed dataset writes advance history. Source failures, spending caps, output truncation, exhausted deadlines and unreached inputs preserve the previous baseline. Missing rows never establish removals. Scoring dates and source metadata dates are part of comparison, so a new date can count as a change without a different numeric score.

Scope and limits

  • One to ten exact CVE IDs; maxResults 1–100; maxRunSeconds 30–120.
  • No asset discovery, scanning, exploit instructions or proof of compromise. EPSS is one prioritization signal, not complete organizational risk.
  • FIRST is used for small lookups, not bulk mirroring. Model updates can affect scores; preserve scoring dates and source attribution.
  • Exact output cap equal to the full selected set can be complete; actual truncation cannot.
  • Documented public API routes only. No arbitrary URLs, credentials, proxies or authentication bypasses.
  • HTTP 401/403/429 stops further source requests. At most one paced retry is allowed for a transient 502/503/504 or transport timeout/reset when the deadline permits it.

Pricing

$0.003 per confirmed saved observation, plus the $0.00005 Actor-start event. Failed requests, invalid input, filtered rows and unchanged items skipped by onlyChanges are not billed as result rows. Apify’s displayed pricing and run spending cap govern the run.

EPSS data are provided by FIRST and Empirical Security; optional NVD data are provided by NIST. Public source access is free. Payment covers this Actor’s validation, normalization, comparisons and integrations.

Companion workflows

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

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.

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

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.

Integrations and support

Use the same small input with Apify tasks, schedules, webhooks, API, MCP or CSV/JSON exports. Include source timing, nvdStatus and SUMMARY when passing results to an AI assistant. This Actor is independently maintained by Mayd It and is not endorsed by the source providers.

Source documentation: FIRST EPSS API and NVD developer guidance.

For an issue, include the run link, a small reproducible input and the relevant SUMMARY failure. Never include secrets.