How to Use Red Hat CVE search in Muse Code
Find Red Hat CVE records for a package, product, or advisory, with severity and scoring information. Use it to build a review list before investigating individual vulnerabilities.
Prompts to try with Red Hat CVE search in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use Red Hat CVE search to find openssl CVEs for Red Hat Enterprise Linux 9. Compare the results with our package inventory and write a review table of CVE IDs, severity, and advisory references.
Use Red Hat CVE search to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from Red Hat CVE search and tell me what changed since last week.
Check Red Hat CVE search and summarize what you find in three bullet points.
Pull the newest data from Red Hat CVE search and give me the result as a table.
How to set up Red Hat CVE search in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code 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 Red Hat CVE search
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": "access-redhat-com/vulnerabilities/search", "input": { "cwe": "<cwe>" } }'
Then paste one of the prompts above: Muse Code finds Red Hat CVE search on Spiral, shows the price and runs it.
Red Hat CVE search providers and prices
Spiral runs Red Hat CVE search through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Severity | low, moderate, important, critical, Low, Moderate, Important, or Critical | Red Hat threat severity. | |
| Page size | 1 to 100 | 20 | Results per page (default 20). Lower it when a page of heavily packaged CVEs exceeds the 1 MiB read limit. |
| Min cvss3 score | 0 to 10 | Only CVEs whose Red Hat CVSS v3 score is at least this. |
Every API field of Red Hat Security Data API · Search is on its tool page: open its card above.
What can you do with Red Hat CVE search in Muse Code?
Build remediation reports that connect Red Hat CVEs to reported product status and fixing advisories. A coding agent can compare that evidence with the project's package inventory and produce a reviewable change list.
Prepare an incident brief
Find relevant package CVEs, inspect their reported product status, and summarize the advisories that deliver fixes for an incident review.
Plan a maintenance window
Build a product-specific vulnerability list and connect the findings to fixing advisories. Group the reported fixes into a maintenance review.
Write remediation tickets
Turn package search results into tickets containing the CVE, Red Hat severity, reported product status, and fixing advisory where available.
Review a security update
Start with an advisory, list the vulnerabilities it addresses, and inspect the CVE assessments to explain the update's security purpose.
Maintain a package watchlist
Repeat searches for packages such as openssl or kernel, compare matching CVEs with the previous review, and investigate newly found records.
Count vulnerabilities and updates separately
Use matching CVEs and their advisory references to produce separate counts of vulnerabilities and fixing updates. Explain where one advisory addresses several CVEs.
More on Red Hat CVE search and Muse Code
Overview
Red Hat CVE search in other agents
Questions about Red Hat CVE search in Muse Code
Can Muse Code use Red Hat CVE search?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run Red Hat CVE search like any built-in tool.
How much does Red Hat CVE search cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use Red Hat CVE search in Muse Code?
No. Spiral runs Red Hat CVE search on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up Red Hat CVE search in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while Red Hat CVE search runs?
Red Hat CVE search runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
Does this cover vulnerabilities from every software vendor?
The scope is Red Hat's product portfolio. Red Hat documents queries for any Red Hat product, including products beyond RHEL.
When does Red Hat publish vulnerability information?
Red Hat says it publishes CVE information and scores immediately after assessing disclosed or coordinated vulnerabilities, unless they are under embargo. It also updates machine-readable security data when fixes are released.
Does a CVE record always include a fixed package version?
No. Red Hat documents fixed package information as optional in a CVE record, including cases where multiple source RPMs share an erratum.
Can one advisory cover several vulnerabilities?
Yes. Red Hat advisories can address multiple CVEs, so counting advisories does not give you the number of vulnerabilities fixed.
Does a product-status review include fixes already released?
Yes, but Red Hat separates unresolved package states from releases that delivered fixes. Both are needed to describe the complete reported status of a CVE across products.
Start using Red Hat CVE search in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


