How to Use NVD CVE details in opencode
Fetch one CVE’s description, references, and available severity, weakness, and affected-product data from NVD. Use it to investigate a known vulnerability or document the evidence behind a patch decision.
Prompts to try with NVD CVE details in opencode
Copy an example into opencode, or ask in your own words.
Use NVD CVE details for CVE-2021-44228 and compare its affected-product evidence with the Log4j versions in this project's Maven files. Write a review note with the returned references.
Use NVD CVE details for CVE-2024-3094 and create a Markdown evidence note containing its description, available severity assessments, weakness classifications, and references.
Use NVD CVE details to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from NVD CVE details and tell me what changed since last week.
Check NVD CVE details and summarize what you find in three bullet points.
How to set up NVD CVE details in opencode
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
Leave out --global to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
- Sign in
Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, /mcps starts the same sign-in.
opencode mcp auth spiral
- Check it
Spiral shows as connected.
opencode mcp list
Use the Spiral skill
- Send opencode 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 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 NVD CVE details
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": "nvd-nist-gov/vulnerabilities/cve", "input": { "cve_id": "<cve_id>" } }'
Then paste one of the prompts above: opencode finds NVD CVE details on Spiral, shows the price and runs it.
NVD CVE details providers and prices
Spiral runs NVD CVE details through Alexandria. Open a card for today's price, with every fee included.
What can you do with NVD CVE details in opencode?
Turn dependency versions and scanner-reported CVE IDs into a review document backed by NVD evidence. Compare available product applicability, severity assessments, and references with the project's files to identify items that need investigation.
Prepare a patch review
Find CVEs for deployed products, investigate known IDs, and review recent revisions. Build a review list with descriptions, available severity assessments, affected-product evidence, and advisory references.
Check dependencies before a release
Compare the application's dependency versions with NVD product applicability data. Look up CVEs already reported by a dependency scanner and identify records that need manual review.
Write a security operations digest
Summarize newly published or changed records for the operations team. Investigate selected CVE IDs and highlight available CISA KEV information alongside severity assessments.
Maintain vulnerability review evidence
Keep the CVE descriptions, weakness classifications, product applicability evidence, and references used in security reviews. Refresh known records and discover additional records through product searches and recent changes.
Draft a product advisory brief
Collect NVD evidence for a public software product and turn relevant CVEs into a readable brief. Separate newly published vulnerabilities from changes to previously reported records.
Identify gaps in vulnerability enrichment
Review known CVEs, product search results, and recent records for missing NIST assessments. Separate records awaiting enrichment from records that already contain assessments supplied by other sources.
More on NVD CVE details and opencode
Overview
NVD CVE details in other agents
Questions about NVD CVE details in opencode
Can opencode use NVD CVE details?
Yes. Add Spiral to opencode as an MCP server, and opencode can find and run NVD CVE details like any built-in tool.
How much does NVD CVE details cost in opencode?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your opencode plan is separate.
Do I need an Alexandria account to use NVD CVE details in opencode?
No. Spiral runs NVD CVE details on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up NVD CVE details in opencode?
About two minutes: add the server, then sign in, then check it.
Does opencode wait while NVD CVE details runs?
NVD CVE details runs in the background. opencode starts the run, checks on it and gives you the json when it's ready.
How quickly does a published CVE appear in NVD?
NVD says CVEs typically appear within an hour of publication to the CVE List. That is the availability of the record, not a promise that severity and affected-product enrichment will be complete.
Why can a public advisory mention a CVE that NVD does not contain?
An advisory can name a CVE before its record is published to the CVE List. NVD does not run the disclosure or CVE publication process, so public mention alone does not mean an NVD record is available.
Does every NVD record have complete severity and product data?
No. Since April 15, 2026, NIST has prioritized enrichment for KEV-listed vulnerabilities, software used by the federal government, and critical software; other CVEs remain listed without immediate enrichment.
Why might a record have a vendor score but no separate NIST score?
NIST no longer routinely adds its own severity score when the submitting CVE Numbering Authority has already supplied one. A missing NIST assessment therefore does not mean the record has no severity assessment.
Do older vulnerabilities all have CVSS v3 scores?
No. NVD says it has no plans to retroactively assess vulnerabilities published before December 20, 2015 with CVSS v3.0 scores.
Start using NVD CVE details in opencode
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into opencode:
set up https://spiral.ai/SKILL.md


