Spiral gives your agent every tool with one account. Browse the tools →

VS Code · Developer

How to Use Red Hat CVE details in VS Code

Get Red Hat's assessment of one CVE, including severity, product fix status, advisories, and available mitigations. Use it to investigate a specific finding across Red Hat products.

Prompts to try with Red Hat CVE details in VS Code

Copy an example into VS Code, or ask in your own words.

Use Red Hat CVE details for CVE-2021-44228. Add a report to this repository showing the reported Red Hat product states and fixing advisories.

Red Hat CVE detailsVS Code
Try asking
  • Use Red Hat CVE details for CVE-2024-6387. Compare the returned product assessment with our RHEL deployment inventory and draft remediation notes.

  • Use Red Hat CVE details 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 details and tell me what changed since last week.

  • Check Red Hat CVE details and summarize what you find in three bullet points.

How to set up Red Hat CVE details in VS Code

Pick the way that suits you. Each takes about two minutes.

Use Spiral's MCP server

  1. Add the hosted server

    Use Add to VS Code on the console's Agents & MCP page, or run:

    code --add-mcp '{"name":"spiral","type":"http","url":"https://api.spiral.ai/mcp"}'
  2. Sign in

    VS Code asks you to sign in when it first starts the server: sign in to Spiral and click Authorize. No API key. Run MCP: List Servers from the Command Palette to check that Spiral is running.

Use the Spiral skill

  1. Send VS Code this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

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

  1. Create an API key

    In the console, under API keys.

  2. Run Red Hat 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": "access-redhat-com/vulnerabilities/cve",
        "input": {
          "cve_id": "<cve_id>"
        }
      }'

Then paste one of the prompts above: VS Code finds Red Hat CVE details on Spiral, shows the price and runs it.

Red Hat CVE details providers and prices

Spiral runs Red Hat CVE details through Alexandria. Open a card for today's price, with every fee included.

AlexandriaDeveloper
Red Hat Security Data API · Cve
access-redhat-com/vulnerabilities/cve

What can you do with Red Hat CVE details in VS 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.

Investigate a scanner finding

Compare a reported CVE with Red Hat's product assessment and the relevant advisory. Identify the vendor evidence needed for a remediation decision.

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.

Document patch evidence

Assemble the advisory's covered products and component versions with the corresponding CVE assessments for a patch review record.

Questions about Red Hat CVE details in VS Code

Can VS Code use Red Hat CVE details?

Yes. Add Spiral to VS Code as an MCP server, and VS Code can find and run Red Hat CVE details like any built-in tool.

How much does Red Hat CVE details cost in VS 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 VS Code plan is separate.

Do I need an Alexandria account to use Red Hat CVE details in VS Code?

No. Spiral runs Red Hat 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 Red Hat CVE details in VS Code?

About two minutes: add the hosted server, then sign in.

Does VS Code wait while Red Hat CVE details runs?

Red Hat CVE details runs in the background. VS 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.

Get started

Start using Red Hat CVE details in VS Code

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into VS Code:

Set up VS Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options