How to Use CVE.org vulnerability record in Zapier
Retrieve a known CVE's description, affected products and versions, references, and available enrichment. Use it to investigate one vulnerability and check the evidence behind an alert.
Prompts to try with CVE.org vulnerability record in Zapier
Copy an example into Zapier, or ask in your own words.
Each Monday, use CVE.org vulnerability record for CVE-2021-44228 and compare its affected products, versions, and references with the previous report.
Every Monday at 9am: use CVE.org vulnerability record to look this up and give me the result as a table.
Pull the latest numbers from CVE.org vulnerability record and tell me what changed since last week.
Check CVE.org vulnerability record and summarize what you find in three bullet points.
Pull the newest data from CVE.org vulnerability record and give me the result as a table.
How to set up CVE.org vulnerability record in Zapier
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send Zapier this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Add an MCP Client connection
In Zapier open Apps, click Add connection and search for MCP Client. Fill in the form:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Zapier never sees it, and you can remove it under Settings › Connected apps in the console.
- Run a Spiral tool in a Zap
Add an MCP Client step to a Zap and choose the Run Tool action with your Spiral connection. Pick a tool: discover finds the right model for a task, estimate_cost prices it and run runs it. For example, run with:
{ "provider": "fal", "model": "fal-ai/flux/schnell", "input": { "prompt": "a lighthouse at dawn" }, "wait": true } - Run CVE.org vulnerability record in a workflow step
Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds CVE.org vulnerability record, prices it and runs it each time the step fires.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run CVE.org vulnerability record
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "cve-org/vulnerabilities/cve_record", "input": { "cve_id": "<cve_id>" } }'
Then paste one of the prompts above: Zapier finds CVE.org vulnerability record on Spiral, shows the price and runs it.
CVE.org vulnerability record providers and prices
Spiral runs CVE.org vulnerability record through Alexandria. Open a card for today's price, with every fee included.
What can you do with CVE.org vulnerability record in Zapier?
Keep a recurring review queue for new CVEs, revised records, and supplier reporting information. A scheduled agent can collect recent changes, revisit selected vulnerability records, and check public CNA listings.
Prepare a daily vulnerability brief
Discover newly published and revised CVEs, investigate selected records, and identify the assigning organizations through the CNA directory.
Review supplier vulnerability evidence
Collect recent CVE changes relevant to Apache or another supplier, inspect affected products and references, and check the assigning CNA's scope.
Investigate advisory corrections
Use updated CVEs to build a review queue, examine their current records, and locate the CNA's public reporting instructions when a correction needs investigation.
Audit CVE assignment provenance
Sample recently changed CVEs, read their assignment metadata, and resolve CNA short names into organizations and scopes for an evidence report.
Review dependencies before a release
Compare affected products and versions in selected CVE records with a project's dependency inventory, using recent changes to find additional records worth checking.
Revisit existing vulnerability tickets
Match recently updated CVE identifiers against an existing ticket list, then retrieve current records to review affected versions and supporting references.
More on CVE.org vulnerability record and Zapier
Overview
CVE.org vulnerability record in other agents
Questions about CVE.org vulnerability record in Zapier
Can Zapier use CVE.org vulnerability record?
Yes. Add Spiral to Zapier as an MCP server, and Zapier can find and run CVE.org vulnerability record like any built-in tool.
How much does CVE.org vulnerability record cost in Zapier?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Zapier plan is separate.
Do I need an Alexandria account to use CVE.org vulnerability record in Zapier?
No. Spiral runs CVE.org vulnerability record on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up CVE.org vulnerability record in Zapier?
About two minutes: add an MCP Client connection, then sign in to Spiral and approve, then run a Spiral tool in a Zap.
Does Zapier wait while CVE.org vulnerability record runs?
CVE.org vulnerability record runs in the background. Zapier starts the run, checks on it and gives you the json when it's ready.
Does CVE include unpublished vulnerability details?
The CVE Program catalogs publicly disclosed vulnerabilities. An identifier marked RESERVED can exist before its vulnerability details are published.
How quickly does CVE.org information change?
The official CVE repository updates about every seven minutes. CNA organization information follows a different schedule: the organization guide says website updates occur on Tuesdays.
How much recent change history does the source retain?
The official repository's deltaLog.json normally keeps a rolling 30 days of record modification history. That window describes the change log, not the age of vulnerabilities in the CVE catalog.
What information identifies an affected vulnerability?
CVE JSON records include the CVE identifier, affected products and versions, and public references. Those references provide the supporting reports and advisories for further investigation.
How do I choose the right CNA for a product?
Choose a CNA whose published scope includes the affected product. CVE.org partner profiles provide reporting instructions, including disclosure policy and contact links.
Start using CVE.org vulnerability record in Zapier
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Zapier:
set up https://spiral.ai/SKILL.md


