[Integrations](https://spiral.ai/integrations) › [Amp](https://spiral.ai/integrations/amp) › [Red Hat CVE details](https://spiral.ai/integrations/amp/red-hat-cve-details)

# How to Use Red Hat CVE details in Amp

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.

|  |  |
| --- | --- |
| Model | Red Hat CVE details |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Red Hat CVE details in Amp

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

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

### Use Spiral's MCP server

1. **Add the server**: No header and no client ID or secret: Amp registers itself with Spiral.

```bash
amp mcp add spiral https://api.spiral.ai/mcp
```

2. **Sign in**: Start `amp`. Amp opens Spiral's sign-in page in your browser: sign in, pick the organization and click Authorize. No API key.

3. **Check it**

```bash
amp mcp doctor
```

### Use the Spiral skill

1. **Send Amp 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.

```bash
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.

```bash
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: Amp finds Red Hat CVE details on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/amp

## Red Hat CVE details tools and prices

- [Red Hat Security Data API · Cve](https://spiral.ai/tools/alexandria/access-redhat-com/vulnerabilities/cve) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | An https://access.redhat.com/security/cve/CVE-... page URL. Mutually exclusive with cve_id. Pattern: ^https?://. |
| cve_id |  | — | CVE id, e.g. CVE-2021-44228 (case-insensitive). Give cve_id or url. Pattern: ^\s*[Cc][Vv][Ee]-[0-9]{4}-[0-9]{4,19}\s*$. |

## What can you do with Red Hat CVE details in Amp?

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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Amp guides](https://spiral.ai/integrations/amp)

## Red Hat CVE details in other agents

- [ChatGPT](https://spiral.ai/integrations/chatgpt/red-hat-cve-details)
- [Claude](https://spiral.ai/integrations/claude-desktop/red-hat-cve-details)
- [Claude Code](https://spiral.ai/integrations/claude-code/red-hat-cve-details)
- [Cline](https://spiral.ai/integrations/cline/red-hat-cve-details)
- [Codex](https://spiral.ai/integrations/codex/red-hat-cve-details)
- [Cursor](https://spiral.ai/integrations/cursor/red-hat-cve-details)
- [Devin](https://spiral.ai/integrations/devin/red-hat-cve-details)
- [dots](https://spiral.ai/integrations/dots/red-hat-cve-details)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/red-hat-cve-details)
- [Gemini](https://spiral.ai/integrations/gemini/red-hat-cve-details)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/red-hat-cve-details)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/red-hat-cve-details)
- [goose](https://spiral.ai/integrations/goose/red-hat-cve-details)
- [Grok](https://spiral.ai/integrations/grok/red-hat-cve-details)
- [Grok Build](https://spiral.ai/integrations/grok-build/red-hat-cve-details)
- [Hermes](https://spiral.ai/integrations/hermes/red-hat-cve-details)
- [Instinct](https://spiral.ai/integrations/instinct/red-hat-cve-details)
- [Manus](https://spiral.ai/integrations/manus/red-hat-cve-details)
- [Muse](https://spiral.ai/integrations/muse/red-hat-cve-details)
- [Muse Code](https://spiral.ai/integrations/muse-code/red-hat-cve-details)
- [n8n](https://spiral.ai/integrations/n8n/red-hat-cve-details)
- [Notion](https://spiral.ai/integrations/notion/red-hat-cve-details)
- [OpenClaw](https://spiral.ai/integrations/openclaw/red-hat-cve-details)
- [opencode](https://spiral.ai/integrations/opencode/red-hat-cve-details)
- [Perplexity](https://spiral.ai/integrations/perplexity/red-hat-cve-details)
- [Raycast](https://spiral.ai/integrations/raycast/red-hat-cve-details)
- [VS Code](https://spiral.ai/integrations/vscode/red-hat-cve-details)
- [Windsurf](https://spiral.ai/integrations/windsurf/red-hat-cve-details)
- [Zapier](https://spiral.ai/integrations/zapier/red-hat-cve-details)

## More Amp guides

- [Read the Docs project details](https://spiral.ai/integrations/amp/read-the-docs-project-details)
- [Red Hat CVE search](https://spiral.ai/integrations/amp/red-hat-cve-search)
- [Read the Docs page index](https://spiral.ai/integrations/amp/read-the-docs-page-index)
- [Red Hat security advisory](https://spiral.ai/integrations/amp/red-hat-security-advisory)
- [Read the Docs documentation search](https://spiral.ai/integrations/amp/read-the-docs-documentation-search)
- [Semantic Scholar author publications](https://spiral.ai/integrations/amp/semantic-scholar-author-publications)

## Questions about Red Hat CVE details in Amp

**Can Amp use Red Hat CVE details?**

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

**How much does Red Hat CVE details cost in Amp?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Amp plan is separate.

**Do I need an Alexandria account to use Red Hat CVE details in Amp?**

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 Amp?**

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

**Does Amp wait while Red Hat CVE details runs?**

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

