How to Use CISA KEV CVE lookup in Codex
Check specific CVE IDs against CISA's catalog and retrieve matching vulnerability details, ransomware status, required actions, and due dates. Use it to investigate CVEs already identified by a scanner or advisory.
Prompts to try with CISA KEV CVE lookup in Codex
Copy an example into Codex, or ask in your own words.
Use CISA KEV CVE lookup to check CVE-2021-44228 and CVE-2021-45046, then compare matching records with this project's dependency inventory and draft remediation notes.
Use CISA KEV CVE lookup for CVE-2023-34362 and draft a remediation ticket fixture containing the returned product, ransomware status, required action, and references.
Use CISA KEV CVE lookup to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from CISA KEV CVE lookup and tell me what changed since last week.
Check CISA KEV CVE lookup and summarize what you find in three bullet points.
How to set up CISA KEV CVE lookup in Codex
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
codex mcp add spiral --url https://api.spiral.ai/mcp
- Sign in
Codex opens the browser: sign in to Spiral and click Authorize. No API key. codex mcp list then shows Spiral.
codex mcp login spiral
Use the Spiral skill
- Send Codex 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 CISA KEV CVE lookup
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": "cisa-gov/vulnerabilities/kev_lookup", "input": { "cve_ids": [ "<cve_ids>" ] } }'
Then paste one of the prompts above: Codex finds CISA KEV CVE lookup on Spiral, shows the price and runs it.
CISA KEV CVE lookup providers and prices
Spiral runs CISA KEV CVE lookup through Alexandria. Open a card for today's price, with every fee included.
What can you do with CISA KEV CVE lookup in Codex?
Turn CISA KEV records into patch ticket drafts tied to the project's scanner findings or dependency inventory. A coding agent can match CVE IDs, attach CISA's required actions, and organize relevant records by due date.
Prioritize scanner findings
Match scanner CVEs against CISA records and put confirmed KEV matches into a remediation review with the required actions and due dates.
Prepare patch tickets
Turn relevant catalog records into ticket drafts containing the CVE, affected product, vulnerability description, required action, and supporting references.
Review ransomware exposure
Identify records marked as known ransomware use within a CVE list, recent additions, or a vendor review, then compare affected products with the organization's inventory.
Plan remediation work
Arrange relevant KEV records by due date and required action to prepare a patch planning meeting.
Write technology-specific security briefings
Summarize exploited vulnerabilities affecting technologies such as Microsoft Exchange, Ivanti Connect Secure, or Apache Log4j, with descriptions and remediation references.
Review recurring software weaknesses
Organize relevant KEV records by their reported CWE codes to support an engineering discussion about recurring weakness types.
Prepare a vendor remediation review
Collect relevant records for a software supplier and use CISA's required actions and linked references to prepare specific questions about remediation.
More on CISA KEV CVE lookup and Codex
Overview
CISA KEV CVE lookup in other agents
Questions about CISA KEV CVE lookup in Codex
Can Codex use CISA KEV CVE lookup?
Yes. Add Spiral to Codex as an MCP server, and Codex can find and run CISA KEV CVE lookup like any built-in tool.
How much does CISA KEV CVE lookup cost in Codex?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Codex plan is separate.
Do I need an Alexandria account to use CISA KEV CVE lookup in Codex?
No. Spiral runs CISA KEV CVE lookup on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up CISA KEV CVE lookup in Codex?
About two minutes: add the hosted server, then sign in.
Does Codex wait while CISA KEV CVE lookup runs?
CISA KEV CVE lookup runs in the background. Codex starts the run, checks on it and gives you the json when it's ready.
Does CISA KEV contain every disclosed vulnerability?
No. CISA requires reliable evidence of exploitation in the wild and a clear remediation action before inclusion, so KEV covers a narrower set of vulnerabilities.
How often does CISA update the catalog?
Updates typically happen on weekdays during normal US Eastern business hours when CISA has new or updated entries. That is a typical publishing pattern, not a fixed daily release.
Does the date added show when exploitation began?
No. It records when CISA added the vulnerability to KEV, so a recent addition does not establish a recent discovery or first attack.
Does Unknown ransomware status mean no ransomware use?
No. CISA defines Unknown as lacking confirmation that the vulnerability has been used for ransomware.
Can I see how an existing KEV record changed?
The catalog file has no accessible inline revision log. CISA's public GitHub repository preserves commit history that can help identify changes to existing entries.
Start using CISA KEV CVE lookup in Codex
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Codex:
set up https://spiral.ai/SKILL.md


